Summary: | sys-devel/crossdev-0.9.19: crossdev -s4 avr does not create avr-g++ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stoian Ivanov <sdr> |
Component: | [OLD] Development | Assignee: | Embedded Gentoo Team <embedded> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chaujc, s, toolchain, walch.martin |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Forcing the latest versions of {binutils,gcc}-config/gnuconfig
Emerging cross-binutils ... Emerging cross-gcc-stage1 ... Emerging cross-avr-libc |
Description
Stoian Ivanov
2009-09-24 17:07:45 UTC
Same problem here. Crossdev automatically adds cross-dev/avr-gcc nocxx (and many other flags) to package.use. It also kills any other line for avr-gcc. Same problem here. Workaround is to use the following command instead: USE="-hardened -nocxx" crossdev -s4 -t avr This command also has crossdev to add "-nocxx" to its entries in "/etc/portage/package.use", which overrides the "nocxx" that remains there. (Note that I'm on the hardened profile on my computer, so I also have to remove the hardened use flag since cross-avr/gcc does not appear to build with the hardened flag; but that's a different bug.) An alternate workaround that I found at <http://jeremah.co.uk/linux/arduino_on_gentoo.html> is to run this command afterwards: USE='-nocxx' emerge cross-avr/gcc crossdev in git has switched avr to stage2-gcc by default and only disables fortran by default now None of the workarounds I've found have worked for me; it does not produce an avr-g++. This is quite a blocker for arduino. USE="-openmp" crossdev -s4 avr is adequate to get a working avr-gcc, but not g++. Why?!? Same problem here. Crossdev runs well without error or warnings, Nevertheless equo isntall arduino complains about missing avr-g++ (In reply to comment #5) > None of the workarounds I've found have worked for me; it does not produce an > avr-g++. This is quite a blocker for arduino. > > USE="-openmp" crossdev -s4 avr > > is adequate to get a working avr-gcc, but not g++. Why?!? > Can we reopen it? no one has provided any actual log files. avr-g++ installs just fine for me. Created attachment 270825 [details]
Forcing the latest versions of {binutils,gcc}-config/gnuconfig
lappy rob # crossdev -s4 avr
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
* 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: /usr/local/portage
* 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 ...
Created attachment 270827 [details]
Emerging cross-binutils ...
Created attachment 270829 [details]
Emerging cross-gcc-stage1 ...
Created attachment 270831 [details]
Emerging cross-avr-libc
lappy rob # crossdev -s4 avr -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- * 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: /usr/local/portage * 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 ] Comment on attachment 270831 [details]
Emerging cross-avr-libc
none of these logs are useful -- they're all exactly the same. they simply show that you've already installed the packages in question. please read things before posting them.
I had the same issue. After wracking my brain for a while, I discovered that this was due to me having the 'keepwork' feature turned on. crossdev builds stage 1 with 'nocxx'. When it goes to rebuild for stage 2, if the directory is still there, it will skip the compile and go straight to install. I'm noting this here in case some other poor sucker ever runs into the same issue. |