I've noticed that patch

http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/gcc/gcc-9.3/0011-Define-GLIBC_DYNAMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch?h=dunfell
 applied to gcc sources changes default linker path for almost all binaries in 
the prepared image.


However the https://sourceware.org/glibc/wiki/ABIList is ignored in case of 
multilib or usrmerge structure of the image's rootfs.


After some investigations I found the SYSTEMLIBS_DIR constant is dependent on 
${root_prefix} and ${baselib} variables,

where the ${root_prefix} is "/usr" (usrmerge feature is enabled). So finally 
the program interpreter is changed to

/usr/lib/ld-linux-x86-64.so.2 (as example I use x86-64) instead of 
/lib64/ld-linux-x86-64.so.2 according to the glibc ABIList.


Shall the OE core layer be compatible to the glibc ABIList when the usrmerge 
feature is enabled?


Best regards,

Oleksandr Ocheretnyi
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#1063): 
https://lists.openembedded.org/g/openembedded-architecture/message/1063
Mute This Topic: https://lists.openembedded.org/mt/73206869/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to