Dear all,
anyone trying to build inetutils-1.9.1, or from Git head, using
./configure --with-pam --with-wrap --with-shishi
will find that every binary in "src/" is asking for
linux-gate.so.1 => (0xb7706000)
libshishi.so.0 => /usr/lib/libshishi.so.0 (0xb76ad000)
libcrypt.so.1 => /lib/i686/cmov/libcrypt.so.1 (0xb767b000)
libutil.so.1 => /lib/i686/cmov/libutil.so.1 (0xb7676000)
libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7672000)
libresolv.so.2 => /lib/i686/cmov/libresolv.so.2 (0xb765e000)
libnsl.so.1 => /lib/i686/cmov/libnsl.so.1 (0xb7647000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7501000)
librt.so.1 => /lib/i686/cmov/librt.so.1 (0xb74f7000)
libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0xb74e7000)
libgnutls.so.26 => /usr/lib/libgnutls.so.26 (0xb744f000)
libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0xb73db000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0xb73d7000)
libidn.so.11 => /usr/lib/libidn.so.11 (0xb73a5000)
/lib/ld-linux.so.2 (0xb7707000)
libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb738c000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7378000)
This include hostname, inetd, logger, syslogd, tftp, and tftpd! Constrast
this to a correctly reduced inetd:
linux-gate.so.1 => (0xb7710000)
libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb76fb000)
libresolv.so.2 => /lib/i686/cmov/libresolv.so.2 (0xb76e7000)
libnsl.so.1 => /lib/i686/cmov/libnsl.so.1 (0xb76cf000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7589000)
/lib/ld-linux.so.2 (0xb7711000)
It is our responsibility that this situation exists, the reason being
that "src/" contains basic utilities like inetd, logger, syslogd, but
also other composites like rlogind, rshd, and rcp which are using
kerberos support and crypto support. We must attend to this mess,
and I hope to be excused! I dare claim that the above situation is
the main reason why the automated build at NixOS, with libbshishi
activated, grinds to a mysterious halt when launching inetd from
"tests/tftd.sh".
Best regards,
Mats
