Summary: | fortran use-flag breaks sys-devel/gcc-4.1.2 for d and mudflap | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Claes Mogren <cm> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge log gcc-4.1.2
emerge log gcc-4.1.2 d Emerge info |
Description
Claes Mogren
2007-05-25 06:45:22 UTC
Created attachment 120246 [details]
emerge log gcc-4.1.2
Failure with fortran and mudflap enabled
Created attachment 120247 [details]
emerge log gcc-4.1.2 d
Failure with fortran and d
Created attachment 120248 [details]
Emerge info
I had a similar error with a system that needed many updates, and after I upgraded some other packages and it compiled fine. Sometimes I find that this to be the case as I usually use emwrap.sh to just update the toolchain, when at times more is needed before the toolchain can be properly rebuilt. Possible suspects (some of the packages I updated): sys-libs/com_err dev-libs/mpfr sys-devel/m4 YMMV Chris Claes: I just tried this on a few systems with the USE flags you said cause problems and I did not encounter any. Are you sure that this fails in the same spot every time? Looking at the logs it looks really strange since the command works a few lines before, and then randomly it isn't there? I'm using gcc-4.2.2, and it compiles just fine with both fortran and mudflap enabled. (Doesn't seem to have a d use-flag) It did fail at the same place every time back then, but since it works for you, and newer versions of gcc builds fine here too, I guess all is well. Thanks for all your good work! :-) |