Emerging sys-block/nbd-2.9.11 failed on my gentoo box: >>> Emerging (1 of 1) sys-block/nbd-2.9.11 to / * nbd-linux-include.h.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * nbd-2.9.11.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking nbd-2.9.11.tar.bz2 ;-) ... [ ok ] * checking nbd-linux-include.h.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking nbd-2.9.11.tar.bz2 to /usr/vartmp/portage/sys-block/nbd-2.9.11/work >>> Unpacking nbd-linux-include.h.bz2 to /usr/vartmp/portage/sys-block/nbd-2.9.11/work * Applying nbd-2.9.1-headers.patch ... [ ok ] >>> Source unpacked. >>> Compiling source in /usr/vartmp/portage/sys-block/nbd-2.9.11/work/nbd-2.9.11 ... * econf: updating nbd-2.9.11/config.sub with /usr/share/gnuconfig/config.sub * econf: updating nbd-2.9.11/config.guess with /usr/share/gnuconfig/config.guess ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-lfs --enable-syslog --build=i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking whether Large File Support should be enabled... yes checking whether syslog logging is requested... yes checking whether a debugging version is requested... no checking for klcc... not found checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. !!! Please attach the following file when seeking support: !!! /usr/vartmp/portage/sys-block/nbd-2.9.11/work/nbd-2.9.11/config.log config.log interesting parts: ... configure:2772: $? = 0 configure:2779: i686-pc-linux-gnu-gcc -V >&5 i686-pc-linux-gnu-gcc: '-V' option must have argument configure:2782: $? = 1 configure:2805: checking for C compiler default output file name configure:2832: i686-pc-linux-gnu-gcc -march=athlon-xp -O2 -pipe -funroll-loops -fprefetch-loop-arrays -fforce-addr -mno-tls-direct-seg-refs /usr/vartmp/portage/sys-block/nbd-2.9.11/work/nbd-2.9.11/inc-after conftest.c >&5 /usr/vartmp/portage/sys-block/nbd-2.9.11/work/nbd-2.9.11/inc-after: file not recognized: Is a directory collect2: ld returned 1 exit status ... ac_cv_env_CFLAGS_value='-march=athlon-xp -O2 -pipe -funroll-loops -fprefetch-loop-arrays -fforce-addr -mno-tls-direct-seg-refs /usr/vartmp/portage/sys-block/nbd-2.9.11/work/nbd-2.9.11/inc-after' ... CFLAGS='-march=athlon-xp -O2 -pipe -funroll-loops -fprefetch-loop-arrays -fforce-addr -mno-tls-direct-seg-refs /usr/vartmp/portage/sys-block/nbd-2.9.11/work/nbd-2.9.11/inc-after' ... Directory inc-after was inserted to CFLAGS! But when I remove line "append-flags -idirafter "${S}"/inc-after" in ebuild, everything is OK! Why this directory was appended to flags? gcc version 4.2.4 (Gentoo Hardened 4.2.4-r1 p1.0, ssp-builtin, pie-9.0.9) glibc-2.7-r2 hardened
read the ebuild/ChangeLog if you want to know what the flag is for it would appear your bash is broken run `emerge nbd --debug` and post the output as an attachment
Sorry for month long delay. This error was inflicted by probably broken hardened version flag-o-matic which just eat -idirafter from CFLAGS. Original flag-o-matic from portage is OK. Sorry for noise.
