I run $ USE="-openmp" crossdev -t avr -s4 -S --without-headers as per Arduino Gentoo manual And the output is: -------------------------------------------------------------------------------------------------- * crossdev version: 20141030 * Host Portage ARCH: amd64 * Target Portage ARCH: * * Target System: avr * Stage: 4 (C/C++ compiler) * ABIs: default * binutils: binutils-[stable] * gcc: gcc-[stable] * libc: avr-libc-[stable] * CROSSDEV_OVERLAY: /var/lib/layman/science * PORT_LOGDIR: /var/log/portage * PORTAGE_CONFIGROOT: * Portage flags: _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * leaving sys-devel/binutils in /var/lib/layman/science * leaving sys-devel/gcc in /var/lib/layman/science * leaving dev-embedded/avr-libc in /var/lib/layman/science * leaving sys-devel/gdb in /var/lib/layman/science * leaving metadata/layout.conf alone in /var/lib/layman/science _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * Log: /var/log/portage/cross-avr-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-avr-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/portage/cross-avr-avr-libc.log * Emerging cross-avr-libc ... [ ok ] * Log: /var/log/portage/cross-avr-gcc-stage2.log * Emerging cross-gcc-stage2 ... * gcc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-avr-info.log * /var/log/portage/cross-avr-gcc-stage2.log.xz * /mnt/data/tmp//portage/cross-avr/gcc*/temp/gcc-config.logs.tar.xz The problematic log file is /mnt/data/tmp/portage/cross-avr/gcc-4.8.4/temp/build.log Running configure in multilib subdir avr25 pwd: /mnt/data/tmp/portage/cross-avr/gcc-4.8.4/work/build/avr configure: creating cache ./config.cache checking for --enable-version-specific-runtime-libs... no checking build system type... x86_64-pc-linux-gnu checking host system type... avr-unknown-none checking target system type... avr-unknown-none checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for avr-strip... /usr/libexec/gcc/avr/strip 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 for avr-gcc... /mnt/data/tmp/portage/cross-avr/gcc-4.8.4/work/build/./gcc/xgcc -B/mnt/data/tmp/portage/cross-avr/gcc-4.8.4/work/build/./gcc/ -B/usr/avr/bin/ -B/usr/avr/lib/ -isystem /usr/avr/include -isystem /usr/avr/sys-include -mmcu=avr25 checking for C compiler default output file name... configure: error: in `/mnt/data/tmp/portage/cross-avr/gcc-4.8.4/work/build/avr/avr25/libsanitizer': configure: error: C compiler cannot create executables See `config.log' for more details. Makefile:9339: recipe for target 'configure-target-libsanitizer' failed make[1]: *** [configure-target-libsanitizer] Error 1 make[1]: Leaving directory '/mnt/data/tmp/portage/cross-avr/gcc-4.8.4/work/build' Makefile:836: recipe for target 'all' failed make: *** [all] Error 2 How can I fix this? Is it a problem with my compiler or a problem of the crossdev ebuild / tool? Reproducible: Always
Created attachment 404298 [details] emerge --info
Created attachment 404300 [details] /var/log/portage/cross-avr-info.log
Created attachment 404302 [details] /var/log/portage/cross-avr-gcc-stage2.log.xz
Created attachment 404304 [details] /mnt/data/tmp//portage/cross-avr/gcc-4.8.4/temp/gcc-config.logs.tar.xz
*** This bug has been marked as a duplicate of bug 525910 ***
