Summary: | sys-devel/crossdev-20100620: crossdev -s4 avr does not create avr-g++ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Shawn Rutledge <s> |
Component: | [OLD] Development | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | chaujc, s, walch.martin, wyvern5 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
binutils
gcc-stage1 libc stage2 info this time it failed (info) this time it failed (libc) cross-avr-avr-libc.log cross-avr-info.log |
Description
Shawn Rutledge
2010-10-07 08:59:35 UTC
works fine for me. but you didnt post any of the logs that crossdev told you to. # crossdev -C avr # USE=-openmp crossdev avr # avr-g++ --version avr-g++ (Gentoo 4.5.1 p1.1, pie-0.4.5) 4.5.1 crossdev didn't _tell_ me to post any logs because it didn't fail. It just didn't build avr-g++. But here's some logs for you anyway. Created attachment 249878 [details]
binutils
Created attachment 249880 [details]
gcc-stage1
Created attachment 249882 [details]
libc
Created attachment 249883 [details]
stage2
Created attachment 249884 [details]
info
Oops those are pretty useless because I tried to build repeatedly. Will clean, rebuild and post again. (In reply to comment #1) > works fine for me. but you didnt post any of the logs that crossdev told you > to. > > # crossdev -C avr > # USE=-openmp crossdev avr > # avr-g++ --version > avr-g++ (Gentoo 4.5.1 p1.1, pie-0.4.5) 4.5.1 How did you end up with 4.5.1? It's building 4.4.4 for me. Is it dependent on your system gcc? Are you on AMD64? gcc ebuilds use the same file (toolchain.eclass), so there shouldnt be a difference. host arch shouldnt matter either. OK this time (trying the same command line as you did) I got an error: [i7][01:58:45 PM] USE=-openmp crossdev avr ---------------------------------------------------------------------------------------------------------- * crossdev version: 20100620 * Host Portage ARCH: amd64 * Target Portage ARCH: * * Target System: avr * Stage: 4 (C/C++ compiler) * binutils: binutils-[latest] * gcc: gcc-[latest] * libc: avr-libc-[latest] * PORTDIR_OVERLAY: /var/lib/layman/science * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/avr * PORTAGE_TMPDIR: /var/tmp/cross/avr _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ] * 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 ... * avr-libc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-avr-info.log * /var/log/portage/cross-avr-avr-libc.log But I'm sure I can also reproduce the case where it doesn't fail, but doesn't produce g++ either. Will attach logs for this round. Created attachment 249889 [details]
this time it failed (info)
Created attachment 249890 [details]
this time it failed (libc)
Well it made a liar out of me and built avr-g++ this time. [i7][02:39:32 PM] USE="-openmp" crossdev -t avr -s4 -S --without-headers --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- * crossdev version: 20100620 * Host Portage ARCH: amd64 * Target Portage ARCH: * * Target System: avr * Stage: 4 (C/C++ compiler) * binutils: binutils-[stable] * gcc: gcc-[stable] * libc: avr-libc-[stable] * PORTDIR_OVERLAY: /var/lib/layman/science * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/avr * PORTAGE_TMPDIR: /var/tmp/cross/avr _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ] * 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 ... [ ok ] So all I can say is that IF I have done a clean first, and IF I use that exact command line, it can work. Whereas leaving it to the defaults does not work. And besides that, there is still the need for the -openmp USE flag, which ought to be defaulted in the ebuild (but I think that's been reported already as another bug). So it still seems to me a bug that it didn't just work the first time, but at least I finally got an avr-g++ after so many attempts. np. glad it worked for you. Created attachment 290443 [details]
cross-avr-avr-libc.log
My cross-avr-avr-libc.log log file
Created attachment 290445 [details]
cross-avr-info.log
cross-avr-info.log log file
I'm having a similar problem. I've attached my log files, the relevant part seems to be this /var/tmp/portage/cross-avr/avr-libc-1.6.2/temp/ccLj5rr8.s: Assembler messages: /var/tmp/portage/cross-avr/avr-libc-1.6.2/temp/ccLj5rr8.s: Error: .size expression for strlcat_P does not evaluate to a constant avr-gcc -I/var/tmp/portage/cross-avr/avr-libc-1.6.2/work/avr-libc-1.6.2/common -I/var/tmp/portage/cross-avr/avr-libc-1.6.2/work/avr-libc-1.6.2/include -x assembler-with-cpp -Wa,-gstabs -mmcu=avr2 -D__COMPILING_AVR_LIBC__ -c /var/tmp/portage/cross-avr/avr-libc-1.6.2/work/avr-libc-1.6.2/libc/pmstring/strlen_P.S make[5]: *** [strlcat_P.o] Error 1 Andrew: Don't know why it fails, but three days ago I've trying to connect my arduino to my gentoo and I had exacly the same problem try avr-libc-1.7.0 |