Le 30/12/2019 à 08:55, Pierre Labastie a écrit : > Le 30/12/2019 à 07:17, Bruce Dubbs a écrit : >> On 12/29/19 10:41 PM, Alan Feuerbacher wrote: >>> >>> On 12/29/2019 4:28 PM, Bruce Dubbs wrote: >>>> On 12/29/19 4:57 PM, Ken Moffat wrote: >>>>> On Sun, Dec 29, 2019 at 09:02:34PM +0000, Ken Moffat wrote: >>>>>> On Sun, Dec 29, 2019 at 01:40:17PM -0600, Bruce Dubbs wrote: >>>>>>> On 12/29/19 12:03 PM, Alan Feuerbacher wrote: >>>>>>>> On 12/29/2019 9:35 AM, Bruce Dubbs wrote: >>>>>>>>> On 12/29/19 9:45 AM, Alan Feuerbacher wrote: >>>>>>>>> >>>>>>>>> What do you get for "ldd /tools/bin/python3" ? >>>>>>>>> >>>>>>>>> -- Bruce >>>>>>>> >>>>>>>> (lfs chroot) root:/tools/bin# ldd /tools/bin/python3 >>>>>>>> linux-vdso.so.1 (0x00007ffcc9e82000) >>>>>>>> libcrypt.so.2 => not found >>>>>>>> libpthread.so.0 => /tools/lib/libpthread.so.0 >>>>>>>> (0x00007f8eaa69b000) >>>>>>>> libdl.so.2 => /tools/lib/libdl.so.2 (0x00007f8eaa696000) >>>>>>>> libutil.so.1 => /tools/lib/libutil.so.1 (0x00007f8eaa691000) >>>>>>>> libm.so.6 => /tools/lib/libm.so.6 (0x00007f8eaa54e000) >>>>>>>> libc.so.6 => /tools/lib/libc.so.6 (0x00007f8eaa390000) >>>>>>>> /lib64/ld-linux-x86-64.so.2 => /tools/lib64/ld-linux-x86- >>>>>>>> 64.so.2 (0x00007f8eaa6be000) >>>>>>>> >>>>>>> >>>>>>> 'libcrypt.so.2 => not found' is enough to prevent the application from >>>>>>> running. libcrypt.so.1 should have been installed by glibc. I do not >>>>>>> know >>>>>>> why python is looking for libcrypt.so.2. Is that from your host? >>>>>>> >>>>>> >>>>>> Is Alan building on fedora-30 or later ? >>>>>> >>>>>> A gurgle for libcrypt.so.2 found >>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1666033 >>>>>> >>>>>> Apparently fedora have moved to libxcrypt. There is a >>>>>> libxcrypt-compat package which installs libcrypt.so.1. >>>>>> Whether installing that on the host will help for LFS >>>>>> I have no idea, but I suspect it won't be that simple. >>>>>> >>>>>> Looking at https://github.com/pypa/manylinux/issues/305 >>>>>> I suspect that this might be problematic. But probably >>>>>> only for python. >>>>>> >>>>>> And the reasoning for the change is at >>>>>> https://fedoraproject.org/wiki/Changes/FullyRemoveDeprecatedAndUnsafeFunctionsFromLibcrypt >>>>>> >>>>>> >>>>>> ĸen >>>>> >>>>> Perhaps, before building python in /tools, >>>>> ln -sv libcrypt.so.1 /tools/libcrypt.so.2 >>>>> (just a suggestion, I've no way of testing it) >>>> >>>> I don't see that. Glibc-2.30 in section 5.7 should create libcrypt.so.1 in >>>> /tools/lib. >> >>> I'm building with Fedora 31. >> >> Alan, that doesn't make any difference. We are building with our own >> source. >> Nothing in /tools should be from the host distro. >> > > Hmmm, except if the Python build system somehow uses the library on the host > (nightmare coming again?)... >
Hopefully not: I've tried a jhalfs build on fedora 31, and python3 is linked to libcrypt.so.1. So, I think that something went wrong when the OP compiled python in chapter 5 (either the lfs environment was not set, or something was wrong in that environment). Pierre -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
