RFC: Generate lib-names.h and stubs.h from ABI-LIST

H.J. Lu hjl.tools@gmail.com
Thu May 24 22:47:00 GMT 2012


On Thu, May 24, 2012 at 3:21 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Thu, May 24, 2012 at 3:18 PM, Joseph S. Myers
> <joseph@codesourcery.com> wrote:
>> On Thu, 24 May 2012, H.J. Lu wrote:
>>
>>> > Anyway, that information should not be repeated in makefiles.  It's
>>> > already in shlib-versions and everything should just get it from
>>> > there.  The makefiles can give for each ABI the tuple to match in
>>> > shlib-versions, akin to the ABI entries in shlib-versions.
>>>
>>> The problem is x86-64 build won't see sysdeps/x86_64/x32/shlib-versions
>>> and x32 build won't see sysdeps/x86_64/64/shlib-versions.  i386 build
>>> won't see neither.  How does it work?
>>
>> Put them all in sysdeps/x86/shlib-versions, where sysdeps/x86 is a new
>> directory shared by all three ABIs (we know we want such directories
>> anyway to get them all using the same installed headers).
>>
>
> sysdeps/x86_64/64/shlib-versions has
>
> x86_64-.*-linux.*       DEFAULT                 GLIBC_2.2.5
> x86_64-.*-linux.*       ld=ld-linux-x86-64.so.2 GLIBC_2.2.5
>
> sysdeps/x86_64/x32/shlib-versions has
>
> x86_64-.*-linux.*       DEFAULT                 GLIBC_2.16
> x86_64-.*-linux.*       ld=ld-linux-x32.so.2    GLIBC_2.16
> x86_64-.*-.*            ABI                     x32-@OS@
>
> Which one to use for x86-64 and x32 builds?

The only issue is ld=soname.  I can try to remove the soname part
and use abi-ld-soname in CPU/Makefile instead.

-- 
H.J.



More information about the Libc-alpha mailing list