On Sat, Dec 15, 2018 at 5:14 PM Bruce Dubbs via blfs-dev <[email protected]> wrote: > > On 12/15/2018 05:48 PM, Roger Koehler via blfs-dev wrote: > > On Sat, Dec 15, 2018 at 4:30 PM Bruce Dubbs via blfs-dev > > <[email protected]> wrote: > >> > >> On 12/15/2018 05:20 PM, Roger Koehler via blfs-dev wrote: > >>> On Sat, Dec 15, 2018 at 3:39 PM Roger Koehler <[email protected]> > >>> wrote: > >>>> > >>>> On Sat, Dec 15, 2018 at 3:18 PM Ken Moffat via blfs-dev > >>>> <[email protected]> wrote: > >>>>> > >>>>> On Sat, Dec 15, 2018 at 03:06:27PM -0700, Roger Koehler via blfs-dev > >>>>> wrote: > >>>>>> On Sat, Dec 15, 2018 at 2:49 PM Ken Moffat via blfs-dev > >>>>>> <[email protected]> wrote: > >>>>>>> > >>>>>>> On Sat, Dec 15, 2018 at 02:06:25PM -0700, Roger Koehler via blfs-dev > >>>>>>> wrote: > >>>>>>>> configure can't file libnettle for some reason. > >>>>>>> > >>>>>>> Have you installed nettle-3.4.1 ? That version is now the minimum > >>>>>>> required - both of them turned out to be affected by the > >>>>>>> side-channel vulnerability, see > >>>>>>> > >>>>>>> http://lists.gnu.org/archive/html/info-gnu/2018-12/msg00001.html > >>>>>>> > >>>>>>> I have just installed gnutls-3.6.5 on my most recent system, after > >>>>>>> upgrading nettle. > >>>>>> > >>>>>> I just reinstalled Nettle 3.4.1 following the book. All 3 tests pass. > >>>>>> Tried again. Still same configure error. If I am the only one > >>>>>> experiencing this issue, I'll refrain from posting further. > >>>>> > >>>>> I initially tried building gnutle in /tmp, and the initial NETTLE > >>>>> test failed. Then I built nettle and installed that to /tmp/NETTLE > >>>>> : the initial test for NETTLE passed, but a later test to check for > >>>>> nettle_sec_rsa_decrypt failed because configure was linking to > >>>>> libnettle.so and getting the old system version. > >>>>> > >>>>> So in my case I did a straight upgrade. > >>>>> > >>>>> If yours is still failing in the initial NETTLE test, look at > >>>>> config.log and also look at /usr/lib/pkgconfig/nettle.pc to confirm > >>>>> that the version is indeed 3.4.1. > >>>>> > >>>>> Alternatively, if it fails on the later test, check that > >>>>> /usr/lib/nibnettle.so is a symplink to libnettle.so.6.5 (instead of > >>>>> to 6.4). > >>>> > >>>> Bingo: > >>>> > >>>> libnettle: /usr/lib/libnettle.so /usr/lib64/libnettle.so > >>>> roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l > >>>> /usr/lib/libnettle.so > >>>> lrwxrwxrwx 1 root root 16 Nov 26 18:45 /usr/lib/libnettle.so -> > >>>> libnettle.so.6.4 > >>>> roger [ /var/lib/sources/gnutls/gnutls-3.6.5 ]$ ls -l > >>>> /usr/lib64/libnettle.so > >>>> lrwxrwxrwx 1 root root 16 Dec 15 15:02 /usr/lib64/libnettle.so -> > >>>> libnettle.so.6.5 > >>>> > >>>> The install only updated one of the links and apparently didn't update > >>>> the pkgconfig files. > >>> > >>> It looks like Nettle 3.4.1 is only installed in /usr/lib64/. Also, the > >>> book tries to chmod in /usr/lib/ and complains because the files don't > >>> exist (I blew away my old installation). Also, even after running > >>> ldconfig, the gnutls configure script is looking for it in /usr/lib/. > >>> So, the files need to be copied to /usr/lib (after running chmod). > >> > >> LFS 6.5. Creating Directories > >> > >> case $(uname -m) in > >> x86_64) mkdir -v /lib64 ;; > >> esac > >> > >> You did not do that? > > > > Yes. I see those instruction in > > /jhalfs/lfs-commands/chapter06/070-creatingdirs > > > Oops, sorry. I was thinking that there was a symlink between /lib and > /lib64. That's obsolete. However, we do not have /usr/lib64 at all. > Something must have incorrectly created that, unless you are building > 32-bit libraries separately.
I just built another system using jhalfs with the development books. I'll let you know if I run into the same problem. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
