Updating the system doing a emerge -e system fails a udev: >>> Emerging (1 of 1) sys-fs/udev-087-r1 to / * udev-087.tar.bz2 MD5 ;-) ... [ ok ] * udev-087.tar.bz2 RMD160 ;-) ... [ ok ] * udev-087.tar.bz2 SHA1 ;-) ... [ ok ] * udev-087.tar.bz2 SHA256 ;-) ... [ ok ] * udev-087.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking udev-087.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking udev-087.tar.bz2 to /var/tmp/portage/udev-087-r1/work >>> Source unpacked. >>> Compiling source in /var/tmp/portage/udev-087-r1/work/udev-087 ... /usr/bin/x86_64-pc-linux-gnu-ar GENHDR udev_version.h CC udev_device.o CC udev_config.o CC udev_add.o CC udev_remove.o CC udev_db.o CC udev_sysfs.o CC udev_rules.o CC udev_rules_parse.o CC udev_utils.o CC udev_utils_string.o CC udev_utils_file.o CC udev_utils_run.o CC udev_libc_wrapper.o AR libudev.a RANLIB libudev.a CC udev.o LD udev STRIP udev CC udevd.o LD udevd STRIP udevd CC udevsend.o LD udevsend STRIP udevsend CC udevcontrol.o LD udevcontrol STRIP udevcontrol CC udevmonitor.o udevmonitor.c: In function 'init_udev_monitor_socket': udevmonitor.c:53: warning: implicit declaration of function 'offsetof' udevmonitor.c:53: warning: nested extern declaration of 'offsetof' udevmonitor.c:53: error: expected expression before 'struct' make: *** [udevmonitor.o] Error 1 !!! ERROR: sys-fs/udev-087-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile udev-087-r1.ebuild, line 63: Called die !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant. I am using kernel 2.6.19: # uname -a Linux pluto 2.6.19.2 #6 SMP Sat Jan 27 16:43:54 CET 2007 x86_64 Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz GenuineIntel GNU/Linux Reproducible: Always
Sorry, we are not going to fix this. Use udev-104-r7; 087 is buggy and horribly outdated, we need newer version stable for upcoming new release. *** This bug has been marked as a duplicate of bug 159871 ***