On Sat, Dec 9, 2017 at 11:54 AM, <tu...@posteo.de> wrote: > On 12/09 06:27, Alexander Kapshuk wrote: >> On Sat, Dec 9, 2017 at 6:03 PM, <tu...@posteo.de> wrote: >> > Hi, >> > >> > autofs-5.1.3 fails to compile: >> > solfire:/root>emerge -v autofs >> > >> > These are the packages that would be merged, in order: >> > >> > Calculating dependencies... done! >> > [ebuild R ] net-fs/autofs-5.1.3::gentoo USE="libtirpc -dmalloc >> > -hesiod -ldap -mount-locking -sasl" 0 KiB >> > >> > Total: 1 package (1 reinstall), Size of downloads: 0 KiB >> > >> >>>> Verifying ebuild manifests >> >>>> Emerging (1 of 1) net-fs/autofs-5.1.3::gentoo >> >>>> Failed to emerge net-fs/autofs-5.1.3, Log file: >> >>>> '/var/tmp/portage/net-fs/autofs-5.1.3/temp/build.log' >> >>>> Jobs: 0 of 1 complete, 1 failed Load avg: 0.71, 0.95, >> >>>> 0.88 >> > * Package: net-fs/autofs-5.1.3 >> > * Repository: gentoo >> > * Maintainer: d...@gentoo.org >> > * USE: abi_x86_64 amd64 elibc_glibc kernel_linux libtirpc >> > userland_GNU >> > * FEATURES: preserve-libs sandbox userpriv usersandbox >> > * Determining the location of the kernel source code >> > * Found kernel source directory: >> > * /usr/src/linux >> > * Found sources for kernel version: >> > * 4.14.4-RT >> > * Checking for suitable kernel configuration options... >> > [ ok ] >> >>>> Unpacking source... >> >>>> Unpacking autofs-5.1.3.tar.xz to >> >>>> /var/tmp/portage/net-fs/autofs-5.1.3/work >> >>>> Source unpacked in /var/tmp/portage/net-fs/autofs-5.1.3/work >> >>>> Preparing source in >> >>>> /var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3 ... >> > * Running eautoreconf in >> > '/var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3' ... >> > * This package has a configure.in file which has long been deprecated. >> > Please >> > * update it to use configure.ac instead as newer versions of autotools >> > will die >> > * when it finds this file. See https://bugs.gentoo.org/426262 for >> > details. >> > * Running autoconf --force ... >> > [ ok ] >> > * Running autoheader ... >> > [ ok ] >> > * Running elibtoolize in: autofs-5.1.3/ >> >>>> Source prepared. >> >>>> Configuring source in >> >>>> /var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3 ... >> >>>> Working in BUILD_DIR: >> >>>> "/var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3" >> > /var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3/configure >> > --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu >> > --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share >> > --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 >> > --docdir=/usr/share/doc/autofs-5.1.3 --with-confdir=/etc/conf.d >> > --with-mapdir=/etc/autofs --without-dmalloc --without-openldap >> > --with-libtirpc --without-sasl --without-hesiod --disable-mount-locking >> > --disable-ext-env --enable-sloppy-mount --enable-force-shutdown >> > --enable-ignore-busy --with-systemd=/usr/lib/systemd/system >> > RANLIB=/usr/bin/x86_64-pc-linux-gnu-ranlib >> > configure: loading site script /usr/share/config.site >> > checking for binaries in... /usr/bin:/bin:/usr/sbin:/sbin >> > checking for Linux proc filesystem... yes >> > checking location of the init.d directory... /etc/init.d >> > checking for autofs configuration file directory... /etc/conf.d >> > checking for autofs maps directory... /etc/autofs >> > checking for autofs fifos directory... /run >> > checking for autofs flag file directory... /run >> > checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc >> > checking whether the C compiler works... yes >> > checking for C compiler default output file name... a.out >> > checking for suffix of executables... >> > checking whether we are cross compiling... no >> > checking for suffix of object files... o >> > checking whether we are using the GNU C compiler... yes >> > checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes >> > checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none >> > needed >> > checking if libtirpc is requested and available... yes >> > checking for getrpcbyname... yes >> > checking for getservbyname... yes >> > checking if malloc debugging is wanted... no >> > checking for mount... /bin/mount >> > checking for mount.nfs... /sbin/mount.nfs >> > checking for umount... /bin/umount >> > checking for fsck.ext2... /sbin/fsck.ext2 >> > checking for fsck.ext3... /sbin/fsck.ext3 >> > checking for fsck.ext4... /sbin/fsck.ext4 >> > checking for modprobe... /sbin/modprobe >> > checking for flex... /usr/bin/flex >> > checking for bison... /usr/bin/bison >> > checking for ranlib... /usr/bin/x86_64-pc-linux-gnu-ranlib >> > checking for rpcgen... no >> > configure: error: required program RPCGEN not found >> > >> > >> > >> > configure misses rpcgen...and seems not to evaluate the USE of >> > libtirpc. >> > >> > I didn't find any fix/patch online. >> > >> > What goes wrong here? >> > >> > Cheers >> > Meino >> > >> > >> > >> If I'm reading the ebuild quoted below right, if 'libtirpc' is set, it >> is net-libs/libtirpc that meets the dependency, otherwise it is glibc >> compiled with rpc that does that. >> /usr/portage/net-fs/autofs/autofs-5.1.3.ebuild:41,42 >> libtirpc? ( net-libs/libtirpc ) >> !libtirpc? ( elibc_glibc? ( sys-libs/glibc[rpc(-)] ) ) >> >> equery -q u sys-libs/glibc | grep rpc >> +rpc >> >> On my system, rpc is included in glibc: >> equery -q b /usr/bin/rpcgen >> sys-libs/glibc-2.25-r9 >> >> What's the case on your system? >> > > It saus: > >>sudo equery -q b /usr/bin/rpcgen > [1] 7433 exit 1 sudo equery -q b /usr/bin/rpcgen > > That's why configure can't find rpcgen and the whole thing fails (see > above). > > The question is: Why is configure looking for rpcgen despite the fact, > that USE includes libtirpc (see above).
The ebuild is missing a dependency on net-libs/rpcsvc-proto, which provides the rpcgen binary that was removed from glibc-2.26. You can work around the issue by installing net-libs/rpcsvc-proto manually.
