"crossdev -t msp430"" successfully builds cross-msp430-binutils, but then fails on cross-msp430-gcc Reproducible: Always Steps to Reproduce: 1. run "crossdev -t msp430" 2. 3. Actual Results: ...<snip>... * Log: /var/log/portage/cross-msp430-msp430-binutils.log * Emerging cross-msp430-binutils ... [ ok ] * Log: /var/log/portage/cross-msp430-msp430-gcc-stage1.log * Emerging cross-msp430-gcc-stage1 ... * msp430-gcc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-msp430-info.log * /var/log/portage/cross-msp430-msp430-gcc-stage1.log
Created attachment 296617 [details] info file
Created attachment 296619 [details] gcc stage 1 log file
Created attachment 296621 [details] config log file config file is /var/tmp/portage/cross-msp430/msp430-gcc-4.6.1_p20111205/work/build/msp430/libgcc/config.log
This looks like it may have built msp430-binutils without the msp430 specific patch applied. This could have happened if you synced within a period of time where the toolchain-binutils eclass wasn't applying the patch properly. Try wiping the msp430 stuff with `crossdev -C msp430`, resync your portage tree, and start a new crossdev run.
Created attachment 296653 [details] binutils build log The build log for binutils shows multiple patches being applied. There is a complaint about "LINGUAS en" not being supported, but the build seems OK (in spite of it). Per suggestion the following commands have been queued: crossdev -C msp430 eix-sync crossdev -t msp430
(In reply to comment #5) > Created attachment 296653 [details] > binutils build log > > The build log for binutils shows multiple patches being applied. There is a > complaint about "LINGUAS en" not being supported, but the build seems OK (in > spite of it). Then it looks like your system might not have the default profile properly selected for msp430-binutils and therefore some symlinks are missing. You should be able to force it to update to the correct profile using a binutils-config invocation.
The "crossdev -C" ... "crossdev ..." sequence worked and I now have a running msp430-binutils and msp430-gcc Comparing the previous and current build logs for msp430-gcc, binutils are now being found during configure. As you suspected the first msp430-binutils didn't build properly.
(In reply to comment #7) > The "crossdev -C" ... "crossdev ..." sequence worked and I now have a running > msp430-binutils and msp430-gcc > > Comparing the previous and current build logs for msp430-gcc, binutils are now > being found during configure. As you suspected the first msp430-binutils > didn't build properly. Marking as fixed then.
