autofs still depends on the features that were dropped in the latest glibc.
Steps to Reproduce:
1. emerge autofs
In file included from ../include/automount.h:32:0,
../include/rpc_subs.h:19:21: fatal error: rpc/rpc.h: No such file or directory
For attempt #2 I added EXTRA_ECONF="--with-libtirpc" and it didn't try very hard to find libtirpc.
For attempt #3 I added -I/usr/include/tirpc to CFLAGS and the build got further along before it died.
Created attachment 279391 [details]
Created attachment 279393 [details]
Created attachment 279395 [details]
# emerge --info
Portage 2.2.0_alpha43 (default/linux/amd64/10.0, gcc-4.6.1, glibc-2.14-r0, 3.0.0-rc6 x86_64)
System uname: Linux-3.0.0-rc6-x86_64-AMD_Phenom-tm-_II_X4_965_Processor-with-gentoo-2.0.3
Timestamp of tree: Tue, 05 Jul 2011 22:15:01 +0000
dev-lang/python: 2.7.2, 3.2
sys-devel/autoconf: 2.13, 2.68
sys-devel/automake: 1.10.3, 1.11.1-r1
sys-kernel/linux-headers: 2.6.39::gentoo_fixes (virtual/os-headers)
Repositories: gentoo cross gentoo_fixes gnome x11 x11_fixes newstuff
ACCEPT_KEYWORDS="* amd64 ~*"
CFLAGS="-march=barcelona -O2 -pipe -flto"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=barcelona -O2 -pipe -flto"
FEATURES="distlocks fixlafiles parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTDIR_OVERLAY="/usr/portage/local/cross /usr/portage/local/gentoo_fixes /usr/portage/local/gnome /usr/portage/local/x11 /usr/portage/local/x11_fixes /usr/portage/local/newstuff"
USE="3dnow 3dnowext X a52 aac acpi alsa amd64 autoipd avahi bluetooth boost bzip2 cairo cdda cheese consolekit cracklib css cups curl custom-cflags custom-cpuopts custom-optimization cxx dbus dhcpcd dri dts dvd encode exceptions expat fbcon ffmpeg flac fortran gif glib gnome gnutls gpm gstreamer gtk gtk3 icu introspection ipv6 ithreads jpeg lcms libnotify mmx mmxext mp2 mp3 mpeg multilib nautilus ncurses networkmanager nls nptl offensive ogg opengl openmp pam pcre png policykit python3 qt3support readline resolvconf samba speex spell sqlite sse sse2 sse3 ssl svg taglib tcl theora threads tiff udev unicode usb vala vapigen vorbis webm x264 xcb xorg xscreensaver xulrunner xv xvid zeroconf zlib" ALSA_PCM_PLUGINS="*" ELIBC="glibc" INPUT_DEVICES="evdev synaptics" KERNEL="linux" LINGUAS="en" SANE_BACKENDS="*" USERLAND="GNU" VIDEO_CARDS="intel nouveau radeon"
Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
I managed to build autofs completely depending on libtirpc but had to drop yp/nis support as the needed headers for this module are dropped in glibc and I couldn't find any other package providing the functionality. I emailed upstream and asked about how this issue will be handled by them. Let's wait for their answer.
Peter, would it be an option to DEPEND on <glibc-2.14 until a better solution?
(In reply to comment #5)
> Peter, would it be an option to DEPEND on <glibc-2.14 until a better solution?
This is better then nothing. I've added this into autofs-5.0.6-r2.ebuild.
(In reply to comment #6)
> (In reply to comment #5)
> > Peter, would it be an option to DEPEND on <glibc-2.14 until a better solution?
> This is better then nothing. I've added this into autofs-5.0.6-r2.ebuild.
vapier now included a patch by fedora people that revert the exclusion of the needed include files. I did test-build all USE flag combination without problems. Thus, for now, we can drop the DEPEND line you just added to the ebuild.
Dustin, was patch included into 5.0.6? As I see report here tells us that autofs fails with glibc-2.14 and I don't see any new patches from vapier...
(In reply to comment #8)
> Dustin, was patch included into 5.0.6? As I see report here tells us that
> autofs fails with glibc-2.14 and I don't see any new patches from vapier...
I should have dug out the link to vapier's mail on -dev about this right away:
I don't know where vapier exactly did the change, but fact is that the header files are again available.
Though the issue itself is not fixed as glibc upstream wants to drop this and autofs upstream (which closely works with fedora) says right now, we don't see a problem right now.
Ok, everything is back now.