https://sourceware.org/bugzilla/show_bug.cgi?id=22962
--- Comment #14 from David Abdurachmanov <david.abdurachmanov at gmail dot com>
---
Looking at output of ld --verbose
[..]
SEARCH_DIR("=/usr/riscv64-redhat-linux/lib64"); SEARCH_DIR("=/usr/lib64");
SEARCH_DIR("=/usr/local/lib64"); SEARCH_DIR("=/lib64");
SEARCH_DIR("=/usr/riscv64-redhat-linux/lib"); SEARCH_DIR("=/usr/local/lib");
SEARCH_DIR("=/lib"); SEARCH_DIR("=/usr/lib");
[..]
Based on glibc dynamic loader default paths I would expect to see
/usr/lib64/lp64d in this list, but I don't see it.
See: https://sourceware.org/ml/libc-alpha/2018-01/msg00969.html
[..]
+/* If given a path to one of our library directories, adds every library
+ directory via add_dir (), otherwise just adds the giver directory. On
+ RISC-V, libraries can be found in paths ending in:
+ - /lib64/lp64d
+ - /lib64/lp64
+ - /lib (only ld.so)
+ so this will add all of those paths.
+
+ According to Joseph Myers:
+ My reasoning for that would be: generic autoconf-configured (etc.)
+ software may only know about using the lib directory, so you want the
+ lib directory to be searched regardless of the ABI - but it's also
+ useful to be able to e.g. list /usr/local/lib in /etc/ld.so.conf for
all
+ architectures and have that automatically imply /usr/local/lib64/lp64d
+ etc. so that libraries can be found that come from software that does
+ use the ABI-specific directories. */
[..]
Dynamic loader will do some tricks with path ending "lib" and will also incl.
"lib64/<ABI>".
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
