[SOLVED] book 8.4 | Section 6.9. - Glibc-2.29 -- make error "cannot find -lnss_nisplus"?

GeekBoy · 08-31-2019, 01:59 PM

So here is the error.
Any ideas on this one?

Code:

if test -r /usr/include/gnu/stubs-64.h && cmp -s /sources/glibc-2.29/build/stubs.h /usr/include/gnu/stubs-64.h; \
then echo 'stubs.h unchanged'; \
else /usr/bin/install -c -m 644 /sources/glibc-2.29/build/stubs.h /usr/include/gnu/stubs-64.h; fi
stubs.h unchanged
rm -f /sources/glibc-2.29/build/stubs.h
/sources/glibc-2.29/build/elf/sln /sources/glibc-2.29/build/elf/symlink.list
rm -f /sources/glibc-2.29/build/elf/symlink.list
test ! -x /sources/glibc-2.29/build/elf/ldconfig || LC_ALL=C \
  /sources/glibc-2.29/build/elf/ldconfig  \
                        /lib /usr/lib
/sources/glibc-2.29/build/elf/ldconfig: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf: No such file or directory
LD_SO=ld-linux-x86-64.so.2 CC="gcc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include -isystem /usr/include" /usr/bin/perl scripts/test-installation.pl /sources/glibc-2.29/build/
/tools/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lnss_nis
/tools/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lnss_nisplus
collect2: error: ld returned 1 exit status
Execution of gcc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include -isystem /usr/include failed!
The script has found some problems with your installation!
Please read the FAQ and the README file and check the following:
- Did you change the gcc specs file (necessary after upgrading from
  Linux libc5)?
- Are there any symbolic links of the form libXXX.so to old libraries?
  Links like libm.so -> libm.so.5 (where libm.so.5 is an old library) are wrong,
  libm.so should point to the newly installed glibc file - and there should be
  only one such link (check e.g. /lib and /usr/lib)
You should restart this script from your build directory after you've
fixed all problems!
Btw. the script doesn't work if you're installing GNU libc not as your
primary library!
make[1]: *** [Makefile:111: install] Error 1
make[1]: Leaving directory '/sources/glibc-2.29'
make: *** [Makefile:12: install] Error 2

Here is the previous parts before make install

Code:

tar xf glibc-2.29.tar.xz
cd glibc-2.29
patch -Np1 -i ../glibc-2.29-fhs-1.patch
ln -sfv /tools/lib/gcc /usr/lib

case $(uname -m) in
i?86) GCC_INCDIR=/usr/lib/gcc/$(uname -m)-pc-linux-gnu/8.2.0/include
ln -sfv ld-linux.so.2 /lib/ld-lsb.so.3
;;
x86_64) GCC_INCDIR=/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include
ln -sfv ../lib/ld-linux-x86-64.so.2 /lib64
ln -sfv ../lib/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3
;;
esac
rm -f /usr/include/limits.h
mkdir -v build
cd build
CC="gcc -isystem $GCC_INCDIR -isystem /usr/include" \
../configure --prefix=/usr \
--disable-werror \
--enable-kernel=3.2 \
--enable-stack-protector=strong \
libc_cv_slibdir=/lib
unset GCC_INCDIR
make -j4

knudfl · 09-02-2019, 06:12 AM

Quote:

cannot find -lnss_nis
cannot find -lnss_nisplus

libnss.so, libnss_nisplus.so should be present from the previous install, 5.7. Glibc-2.29

sr_ls_boy · 09-02-2019, 07:24 AM

Try Hiroshi Takekawa patch @ this link.

GeekBoy · 09-03-2019, 12:56 AM

Quote:

Originally Posted by knudfl

libnss.so, libnss_nisplus.so should be present from the previous install, 5.7. Glibc-2.29

I reran the compile for section 5.7. Same result.

Quote:

Originally Posted by sr_ls_boy

Try Hiroshi Takekawa patch @ this link.

The patch is for 2.26, 2.27, and 2.28.

We are dealing with 2.29.

Thanks for the both of you for taking the time to respond.

Anyway, I did run it, and no change

sr_ls_boy · 09-03-2019, 07:09 AM

It worked for me with 2.29. You'll have to simply open the patch and hand edit the file yourself.
We're only talking about 1 line that needs changing.

GeekBoy · 09-03-2019, 03:05 PM

I used the 2.28 patch. I redid it, and went in and manually changed the line

from

Code:

 && $name ne "nss_test1" && $name ne "libgcc_s") {

to

Code:

&& $name ne "nss_test1" && $name ne "nss_test2" && $name ne "nss_nis" && $name ne "nss_nisplus" && $name ne "libgcc_s") {

Here is the result:

Code:

test ! -x /sources/glibc-2.29/build/elf/ldconfig || LC_ALL=C \
  /sources/glibc-2.29/build/elf/ldconfig  \
                        /lib /usr/lib
/sources/glibc-2.29/build/elf/ldconfig: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf: No such file or directory
LD_SO=ld-linux-x86-64.so.2 CC="gcc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include -isystem /usr/include" /usr/bin/perl scripts/test-installation.pl /sources/glibc-2.29/build/
/tools/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lnsl
collect2: error: ld returned 1 exit status
Execution of gcc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include -isystem /usr/include failed!
The script has found some problems with your installation!
Please read the FAQ and the README file and check the following:
- Did you change the gcc specs file (necessary after upgrading from
  Linux libc5)?
- Are there any symbolic links of the form libXXX.so to old libraries?
  Links like libm.so -> libm.so.5 (where libm.so.5 is an old library) are wrong,
  libm.so should point to the newly installed glibc file - and there should be
  only one such link (check e.g. /lib and /usr/lib)
You should restart this script from your build directory after you've
fixed all problems!
Btw. the script doesn't work if you're installing GNU libc not as your
primary library!
make[1]: *** [Makefile:111: install] Error 1
make[1]: Leaving directory '/sources/glibc-2.29'
make: *** [Makefile:12: install] Error 2

I still made the first patch in the book as instructed, if that makes any difference.

sr_ls_boy · 09-05-2019, 09:23 AM

I remember now.

So, you added:
&& $name ne "nss_nis" && $name ne "nss_nisplus"
because the test suite cant find:
-lnss_nis
-lnss_nisplus

But now if can't find:
-lnsl
Try adding this:
&& $name ne "nsl"

GeekBoy · 09-05-2019, 11:58 PM

That worked out. It seems there needs to be a new patch for version 2.29/

Thanks a bunch!

Prabhu R · 03-27-2020, 11:25 PM

Quote:

Originally Posted by GeekBoy

I used the 2.28 patch. I redid it, and went in and manually changed the line

from

Code:

 && $name ne "nss_test1" && $name ne "libgcc_s") {

to

Code:

&& $name ne "nss_test1" && $name ne "nss_test2" && $name ne "nss_nis" && $name ne "nss_nisplus" && $name ne "libgcc_s") {

Here is the result:

Code:

test ! -x /sources/glibc-2.29/build/elf/ldconfig || LC_ALL=C \
  /sources/glibc-2.29/build/elf/ldconfig  \
                        /lib /usr/lib
/sources/glibc-2.29/build/elf/ldconfig: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf: No such file or directory
LD_SO=ld-linux-x86-64.so.2 CC="gcc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include -isystem /usr/include" /usr/bin/perl scripts/test-installation.pl /sources/glibc-2.29/build/
/tools/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lnsl
collect2: error: ld returned 1 exit status
Execution of gcc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include -isystem /usr/include failed!
The script has found some problems with your installation!
Please read the FAQ and the README file and check the following:
- Did you change the gcc specs file (necessary after upgrading from
  Linux libc5)?
- Are there any symbolic links of the form libXXX.so to old libraries?
  Links like libm.so -> libm.so.5 (where libm.so.5 is an old library) are wrong,
  libm.so should point to the newly installed glibc file - and there should be
  only one such link (check e.g. /lib and /usr/lib)
You should restart this script from your build directory after you've
fixed all problems!
Btw. the script doesn't work if you're installing GNU libc not as your
primary library!
make[1]: *** [Makefile:111: install] Error 1
make[1]: Leaving directory '/sources/glibc-2.29'
make: *** [Makefile:12: install] Error 2

I still made the first patch in the book as instructed, if that makes any difference.

When building my lfs I encountered the same problem & I did the same thing , Then the problem was solved.
My sincere thanks to all @GeekBoy, @sr_ls_boy. I would like to talk to you, Can you give your contact info. my contact mail id : r.prabhuome2@gmail.com

TheRealGrogan · 04-07-2020, 01:21 AM

I had that happen too, when I built this system. I used glibc 2.30 at the time. It's an artifact of building in the chroot, it doesn't happen when building glibc on the running system.

I also had to add the modules I enabled with --enable-obsolete- to that line in test-installation.pl