On 5/30/2026 6:06 AM, Stefan Schulze Frielinghaus wrote:
> Ping.
>
> On Tue, May 05, 2026 at 10:31:14PM +0200, Stefan Schulze Frielinghaus wrote:
>> From: Stefan Schulze Frielinghaus <[email protected]>
>>
>> While removing multilib support on s390, we still want to maintain a
>> directory structure where 64-bit libraries end-up in directories named
>> "lib64" instead of "lib". In order to do so only make use of
Funny, I stumbled over a similar problem a year or two ago here. I
dropped multilibs from a build, which in turn caused the single
remaining library that got built to land in the main library directory
rather than in the expected subdirectory. In the end once I saw what
happened it was "oh, yea that makes some sense". It was solely an
internal issue (or so I thought) and I just restored the multilibs and
went on to more important things.
In your case you've got a platform with a long history and preserving
that directory layout seems much more important than the case I was
dealing with.
>>
>> in do_spec_1() from gcc.cc. For non-Unix-like OSs' this might not be
>> only superfluous but mandatory because a dot might mean something
>> different and doesn't resolve to the same directory. Any thoughts about
>> this?
Not really, it's well out of my areas of expertise as I've lived in
unix-land for the last 40 years, knowledge of other hosts is limited at
best.
>>
>> Currently I'm running bootstrap+regtest for the following
>> configurations:
>>
>> {--enable-multilib,--disable-multilib} x {Ubuntu,Fedora} x
>> {s390x-with-m31-removed,s390x-without-m31-removed,x86_64}-linux-gnu
>>
>> which will take some time to complete.
It looks generally sensible. I think a cursory investigation of how
other host OSs handle the dot case and the results of your testing
probably drive the integrate as-is or iterate decision.
jeff
