https://sourceware.org/bugzilla/show_bug.cgi?id=22962
--- Comment #3 from Jim Wilson <wilson at gcc dot gnu.org> --- I have a Fedora stage4 disk image that I'm running on qemu, and which has glibc-2.27. Libraries are in /usr/lib64 exactly as I expect. You pointed at part 0 of a 19 part patch set. I'm guessing you are talking about part 19, which adds support to build-many-glibcs.py. This is not an official recommendation on where to place libraries. This is merely a script to enable testing of many different glibc builds. This part of the patch set did not survive to make it into glibc-2.27. The --libdir options were removed. Default library placement is really a matter of distro packaging, not glibc patches. Different distros have different rules on where to place libraries. As long as a distro is consistent there is no problem. Hard coding all of these rules into the linker is not practical. Normally, they get coded into the compiler. It sounds like your compiler was configured wrong for your target OS. -- 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