On Wed, 8 Jan 2020 at 03:12 Pierre Labastie via lfs-dev < [email protected]> wrote:
> > Actually, the static libraries libc.a and libpthread.a should be in > /usr/lib. > Aren't they there? If not, and you have not manually removed them, > something > went wrong during glibc install (or an inadvertent "rm /usr/lib/*.a" or > whatever in the scripts may also explain). But certainly not an upstream > bug. > I also suspect something might have gone wrong with my glibc installation but cannot figure it. Tried it several times to no avail. Must be something subtle. My /usr/lib has no libc.a or libpthread.a. There is a libc_nonshared.a along with some other static libraries listed below: /mnt/jox/usr/lib/libc_nonshared.a /mnt/jox/usr/lib/libmvec_nonshared.a /mnt/jox/usr/lib/libstdc++fs.a /mnt/jox/usr/lib/libg.a /mnt/jox/usr/lib/libncurses++w.a /mnt/jox/usr/lib/libsupc++.a /mnt/jox/usr/lib/libm-2.30.a /mnt/jox/usr/lib/libssp_nonshared.a /mnt/jox/usr/lib/liby.a /mnt/jox/usr/lib/libmcheck.a /mnt/jox/usr/lib/libstdc++.a > Please do not top post in this list, thanks. Apologize for that. Gmail doesn't make it easier neither. > tests are particularly likely to use static libs Can the upstream code be improved by migrating the test to shared library instead? Isn't that something the upstream developers might consider if it is suggested to them?
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
