Summary: | dev-embedded/avr-libc-1.4.4 fails to emerge at configure script | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Manuel Sabban <sabban> |
Component: | Current packages | Assignee: | Henrik Brix Andersen <henrik> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dragonheart, gustavoz, sanchan |
Priority: | High | Keywords: | InVCS |
Version: | 2006.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | It's the log of the configure script |
Description
Manuel Sabban
2006-05-29 02:41:32 UTC
Created attachment 87786 [details]
It's the log of the configure script
I didn't know that "crossdev --target avr" do the trick. Maybe some documentation should be useful, or did I miss something ? If people thinks it's useful I can try to write something. (In reply to comment #2) > I didn't know that "crossdev --target avr" do the trick. Maybe some > documentation should be useful, or did I miss something ? If people thinks it's > useful I can try to write something. How did you get avr-gcc onto your system if not using crossdev? > How did you get avr-gcc onto your system if not using crossdev?
I thought that "emerge avr-libc" would have done it, but it didn't work.
It's not only a 1.4.4 error, masking it and trying to rebuild the toolchain cause the same fail error on 1.3.3. I think there's something wrong about gcc itself. (In reply to comment #5) > It's not only a 1.4.4 error, masking it and trying to rebuild the toolchain > cause the same fail error on 1.3.3. I think there's something wrong about gcc > itself. There's nothing wrong with the toolchain. The avr-libc ebuilds are supposed to be used through crossdev (or at least, you're supposed to have a working avr toolchain installed). I'm working on a proper check for this to put in pkg_setup(). It's not a gcc problem, it's a crossdev problem. Step to obtain a avr-libc emerge success: crossdev -t avr building binutils, gcc and then failing avr-libc. use gcc-config to set avr-3.4.6/vanilla crossdev -t avr here you have avr-libc emerged. It's simply a PATH issue, avr-libc can't find avr-gcc in the PATH, so it fall back on gcc that fails to produce objects for --target=avr. (In reply to comment #7) > It's not a gcc problem, it's a crossdev problem. > Step to obtain a avr-libc emerge success: > > crossdev -t avr > > building binutils, gcc and then failing avr-libc. > > use gcc-config to set avr-3.4.6/vanilla > > crossdev -t avr > > here you have avr-libc emerged. > > It's simply a PATH issue, avr-libc can't find avr-gcc in the PATH, so it fall > back on gcc that fails to produce objects for --target=avr. I can not reproduce that here. Besides, that's an entirely different problem than what this bug report deals with. This bug report is about avr-libc failing when emerged through 'emerge avr-libc' without having an avr toolchain installed. Please open a new bug for the crossdev problem if it persists. (In reply to comment #8) > Besides, that's an entirely different problem > than what this bug report deals with. This bug report is about avr-libc failing > when emerged through 'emerge avr-libc' without having an avr toolchain > installed. > > Please open a new bug for the crossdev problem if it persists. You're right, sorry. I think some more rest would help me avoiding error like this. Reported in bug #136105 I have added a check for 'avr-gcc' and a hint about using crossdev to dev-embedded/avr-libc-1.4.4. Thank you for reporting this. |