Bug 300358 – sys-devel/gcc: USE=mudflap fails for avr targets

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description David Relson 2010-01-10 02:53:25 UTC]

while emerging cross-avr/gcc, the libmudflap configuration step fails with:

configure: error: C compiler cannot create executables


Reproducible: Always

Steps to Reproduce:
1.emerge cross-avr/gcc fails
2.
3.

Actual Results:  
checking whether to enable maintainer-specific portions of Makefiles... no
checking for avr-gcc... /var/tmp/portage/cross-avr/gcc-4.4.2/work/build/./gcc/xgcc -B/var/tmp/portage/cross-avr/gcc-4.4.2/work/build/./gcc/ -B/usr/avr/bin/ -B/usr/avr/lib/ -isystem /usr/avr/include -isystem /usr/avr/sys-include
checking for C compiler default output file name... configure: error: in `/var/tmp/portage/cross-avr/gcc-4.4.2/work/build/avr/libmudflap':
configure: error: C compiler cannot create executables
See `config.log' for more details.
make[1]: *** [configure-target-libmudflap] Error 1
make[1]: Leaving directory `/var/tmp/portage/cross-avr/gcc-4.4.2/work/build'
make: *** [all] Error 2
 * ERROR: cross-avr/gcc-4.4.2 failed:
 *   emake failed with all
 * 
 * Call stack:
 *     ebuild.sh, line   54:  Called src_compile
 *   environment, line 5062:  Called toolchain_src_compile
 *   environment, line 5624:  Called gcc_src_compile
 *   environment, line 3217:  Called gcc_do_make
 *   environment, line 3007:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
 * 
 * If you need support, post the output of 'emerge --info =cross-avr/gcc-4.4.2',
 * the complete build log and the output of 'emerge -pqv =cross-avr/gcc-4.4.2'.
 * This ebuild is from an overlay named 'osage': '/usr/local/portage/'
 * The complete build log is located at '/var/log/portage/cross-avr:gcc-4.4.2:20100110-020728.log'.
 * The ebuild environment file is located at '/var/tmp/portage/cross-avr/gcc-4.4.2/temp/environment'.
 * S: '/var/tmp/portage/cross-avr/gcc-4.4.2/work/build'

[Comment 1 David Relson 2010-01-10 02:54:49 UTC]

Created attachment 215886 [details]
output of "emerge --info cross-avr/gcc-4.4.2"

[Comment 2 David Relson 2010-01-10 02:56:16 UTC]

Created attachment 215888 [details]
output of "emerge -pqv cross-avr.gcc-4.4.2"

[Comment 3 David Relson 2010-01-10 02:58:57 UTC]

Created attachment 215890 [details]
complete build log

[Comment 4 SpanKY 2010-01-10 22:23:12 UTC]

so dont enable USE=mudflap

[Comment 5 SpanKY 2010-01-10 22:32:41 UTC]

crossdev already forces -mudflap onto cross-$CTARGET/avr via per-package use.  if you modify that, then you get the pieces.

$ grep gcc /etc/portage/package.use/cross-avr
cross-avr/gcc -fortran -selinux -boundschecking -d -fortran -gtk -gcj -libffi -mudflap nocxx -objc -objc++ -objc-gc -openmp