Trying to emerge lvm2 fails caused by compilation error for a linux header file. Re-emerging linux header solves the problem Reproducible: Always Steps to Reproduce: 1. emerge -u lvm2 Steps to fix: 1. emerge linux-headers 2. emerge -u lvm2 3. Actual Results: i686-pc-linux-gnu-gcc -c -I. -I../include -march=athlon-xp -O2 -pipe -fomit-frame-pointer -march=athlon-xp -O2 -pipe -fomit-frame-pointer -DLVM1_INTERNAL -DPOOL_INTERNAL -DCLUSTER_LOCKING_INTERNAL -DSNAPSHOT_INTERNAL -DMIRRORED_INTERNAL -DREADLINE_SUPPORT -DDEVMAPPER_SUPPORT -DO_DIRECT_SUPPORT -DHAVE_LIBDL -DHAVE_GETOPTLONG -DHAVE_RL_COMPLETION_MATCHES -fPIC -Wall -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -O2 -march=athlon-xp -O2 -pipe -fomit-frame-pointer -DLVM1_INTERNAL -DPOOL_INTERNAL -DCLUSTER_LOCKING_INTERNAL -DSNAPSHOT_INTERNAL -DMIRRORED_INTERNAL -DREADLINE_SUPPORT -DDEVMAPPER_SUPPORT -DO_DIRECT_SUPPORT -DHAVE_LIBDL -DHAVE_GETOPTLONG -DHAVE_RL_COMPLETION_MATCHES -fPIC -Wall -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -O2 device/dev-io.c -o device/dev-io.o In file included from /usr/include/linux/wait.h:12, from /usr/include/linux/fs.h:12, from device/dev-io.c:34: /usr/include/linux/list.h:44: error: conflicting types for `list_empty' ../include/list.h:61: error: previous declaration of `list_empty' make[1]: *** [device/dev-io.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/var/tmp/portage/portage/lvm2-2.01.09/work/LVM2.2.01.09/lib' make: *** [lib] Error 2 !!! ERROR: sys-fs/lvm2-2.01.09 failed. !!! Function src_compile, Line 28, Exitcode 2 !!! compile problem
> Re-emerging linux header solves the problem So what
> Re-emerging linux header solves the problem So what´s the point of this bug, then? BTW, compiles just fine here.
I think the ebuild should make the step to recompile linux-headers before proceed to compile lvm2 if this is neccesary...
It is not necessary here and for a lot of other people, b/c it works just fine. Also, I can
It is not necessary here and for a lot of other people, b/c it works just fine. Also, I can´t see how the ebuild would know that your linux headers are broken before compiling. ;-)