Bugzilla Bug 12357

# emerge -b bison      
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-devel/bison-1.35 to /
>>> md5 ;-) bison-1.35.tar.gz
>>> Unpacking source...
>>> Unpacking bison-1.35.tar.gz
>>> Source unpacked.
icc
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking for i686-pc-linux-gnu-gcc... iccbin
checking for C compiler default output... configure: error: C compiler cannot 
create executables

!!! ERROR: sys-devel/bison-1.35 failed.
!!! Function src_compile, Line 21, Exitcode 77
!!! (no error message)

Strange.. (and yeah, I'm sure my C compiler works..)

Can you run:

  # gcc --version

?

If not, have a look at:

  http://bugs.gentoo.org/show_bug.cgi?id=12298

or, do the following:

  # env-update; source /etc/profile; hash -r

and try again.  Also, what gcc version and revision ?

  # emerge gentoolkit; epm -q gcc

I'm aware of the portage-r6 issue earlier today, and this one isn't it.  I can 
build everything fine, except bison.  The problem that seems to be with this 
one is that it's trying to use icc, but maybe that doesn't work out so well 
with autoconf?  Not sure.

$ epm -q gcc
gcc-3.2.1
$ gcc -v
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/specs
Configured with: /archive/tmp/portage/gcc-3.2.1/work/gcc-3.2.1/configure --
prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --
host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --target=i686-pc-linux-gnu --
with-system-zlib --enable-languages=c,c++,ada,f77,objc,java --enable-
threads=posix --enable-long-long --disable-checking --enable-cstdio=stdio --
enable-clocale=generic --enable-__cxa_atexit --enable-version-specific-runtime-
libs --with-gxx-include-dir=/usr/include/g++-v32 --with-local-
prefix=/usr/local --enable-shared --enable-nls --without-included-gettext
Thread model: posix
gcc version 3.2.1

Forgot to add, I did try env-update; source /etc/profile; hash -r, and have 
tested icc too (it works) but bison still fails to build.

Do:

 # FEATURES="noclean" emerge bison

and then include the config.log in its build dir.

Please just attach the config.log, thanks.  If you need help with it, let me
know.

Created an attachment (id=6587) [edit]
work/bison-1.35/config.log

config.log for bison-1.35 attached

I think I see the problem, it looks like my CFLAGS are passed to icc and it 
probably bombs out compiling the test program because the flags don't jive with 
icc.

Yep.  You should know that icc will not compile everything out there that
gcc does ...  We can mark this as closed ?

Yeah thats true, though if the ebuild was going to check for icc to build with 
it I'd think it should make sure it works, or not bother.

Not a huge problem though.

Ill rip the icc stuff out of bison ebuild ... sorry, did not see that somebody
added that.

*** Bug 12399 has been marked as a duplicate of this bug. ***