sys-fs/udev-187-r1 ebuild fails Reproducible: Always Steps to Reproduce: 1. emerge -vu udev Actual Results: see the build log for the ebuild failure Expected Results: ebuild succeeds and installs The ebuild fails with: ------------------ make -j1 -f Makefile -f /var/tmp/portage/sys-fs/udev-187-r1/temp/Makefile.extra BUILT_SOURCES GEN src/core/syscall-list.txt GEN src/core/syscall-from-name.gperf GEN src/core/syscall-from-name.h (standard input): No keywords in input file! make: *** [src/core/syscall-from-name.h] Error 1 ---------------- I tried to debug this, there are two steps: --- step 1: $ awk 'BEGIN{ print "struct syscall_name { const char* name; int id; };"; print "%null-strings"; print "%%";} { printf "%s, __NR_%s\n", $$1, $$1 }' </var/tmp/portage/sys-fs/udev-187-r1/work/systemd-187/src/core/syscall-list.txt --- output of step 1: struct syscall_name { const char* name; int id; }; %null-strings %% --- step 2: $ gperf -L ANSI-C -t --ignore-case -N lookup_syscall -H hash_syscall_name -p -C < output_of_step_1 --- output of step 2: (standard input): No keywords in input file! ----- emerge --info output: Portage 2.1.11.9 (default/linux/amd64/10.0, gcc-4.6.3, glibc-2.15-r2, 3.4.7-r1 x86_64) ================================================================= System uname: Linux-3.4.7-r1-x86_64-Intel-R-_Core-TM-2_CPU_L7400_@_1.50GHz-with-gentoo-2.1 Timestamp of tree: Tue, 07 Aug 2012 11:00:01 +0000 app-shells/bash: 4.2_p37 dev-lang/python: 2.7.3-r2, 3.2.3-r1 dev-util/cmake: 2.8.8-r3 dev-util/pkgconfig: 0.27 sys-apps/baselayout: 2.1-r1 sys-apps/openrc: 0.10.5 sys-apps/sandbox: 2.6 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.9.6-r3, 1.11.6 sys-devel/binutils: 2.22.90 sys-devel/gcc: 4.6.3 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4.2 sys-devel/make: 3.82-r3 sys-kernel/linux-headers: 3.5 (virtual/os-headers) sys-libs/glibc: 2.15-r2 Repositories: gentoo x-portage-overlay ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=core2 -O2 -fomit-frame-pointer -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles news parallel-fetch parse-eapi-ebuild-head protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch" FFLAGS="-O2 -pipe" LANG="en_AU.UTF-8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" LINGUAS="en" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage-overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa amd64 bzip2 dbus gpm idn ipv6 jpeg lzma mmx multilib nptl nptlonly pam sse sse2 sse3 ssl ssse3 threads threadsafe tiff truetype udev unicode xcb xml xorg zlib" ALSA_CARDS="snd-hda-intel" ALSA_PCM_PLUGINS="*" CURL_SSL="openssl" ELIBC="glibc" GRUB_PLATFORMS="pc" INPUT_DEVICES="keyboard mouse evdev synaptics" KERNEL="linux" LINGUAS="en" USERLAND="GNU" VIDEO_CARDS="intel fbdev i915 i965" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
Created attachment 320626 [details] ebuild log
I have gotten to the root of the problem. The error lay in /usr/include/asm/unistd*.h - instead of list of calls it contained a path to /var/tmp/portage/sys-kernel/linux-headers/..... Obviously some sort of an error. I re-installed sys-kernel/linux-headers-3.5 and the files got generated properly this time. Maybe linux-headers had a bug when I installed it but it got fixed without a version bump? I do not know. Anyhow, the problem does not lie with the udev ebuild.
