Re: fixing "libtool -module" for C++

On 3/23/25 8:52 PM, Valery Ushakov wrote:
> On Sun, Mar 23, 2025 at 20:21:27 +0100, Jörg Sonnenberger wrote:
> 
>> On 3/22/25 8:19 AM, Martin Husemann wrote:
>>> I don't know anything about libtool, but not linking with -lgcc *might*
>>> work on some modules on some platforms, but might fail on others
>>> due to CPU differences.
>>
>> More specifically, there is something like millicode on some CPU which is
>> never shared. I'm not 100% sure from memory right now if any of those are
>> left with code in libgcc or if we provide a libc implementation at all times
>> now, but that was a real concern in the past at least.
> 
> "Provide a _libc_ implementation" is a bit unfortunate way to word
> this, I think, as millicode cannot, by design, be provided in some
> other library.

I meant that in the sense of "not getting it from libgcc.a". E.g. on 
Linux, libc.so nowadays is often a linker script that looks for the real 
shared library as well as libc_nonshared.a, which could serve the same 
purpose.

Joerg