[uclibc-ng-devel] Fwd: new uClibc-ng release

These should be going to the list for archiving, so I'm forwarding it. On 4/29/18 8:32 AM, Dave Flogeras wrote: Yes I noticed that, and it is serious, but this is the least of my worries right now. The LDPATH search is totally broken on amd64. ldconfig shows that libstdc++.so and libgcc_s.so are in the search path: # ldconfig -p | grep libstdc++.so libstdc++.so.6 (libc0) => /usr/lib/gcc/x86_64-gentoo-linux-uclibc/6.4.0/libstdc++.so.6 libstdc++.so (libc0) => /usr/lib/gcc/x86_64-gentoo-linux-uclibc/6.4.0/libstdc++.so # ldconfig -p | grep libgcc_s.so libgcc_s.so.1 (libc0) => /usr/lib/gcc/x86_64-gentoo-linux-uclibc/6.4.0/libgcc_s.so.1 And yet a test c++ program cannot locate those libraries: # ldd test libstdc++.so.6 => not found libgcc_s.so.1 => not found libc.so.0 => /lib//libc.so.0 (0x7f6bfb067000) ld64-uClibc.so.0 => /lib/ld64-uClibc.so.0 (0x7f6bfb516000) @Waldemar, the issue is not anything you suggested in your previous email. What might you have touched in ld64-uClibc.so or libc.so itself that would affect the search path? If its any help, I hit the dlclose() issue many years ago (and might have been the first to report it, I'm not sure). There was some size issue wrt 64 vs 32 that cause an issue there. I wonder if in fixing that maybe you broke LDPATH? -- Anthony G. Basile, Ph.D. Gentoo Linux Developer [Hardened] E-Mail : blueness(a)gentoo.org GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA GnuPG ID : F52D4BBA