gcc-4.1.2 does not compile with mudflap or d when fortran is enabled. Besides these three I have doc, gtk and nls enabled in the use flags. I've tested the following combinations: 1) Builds fine with USE="fortran" ("doc gtk nls" are enable in all tests) 2) Fails with USE="fortran mudflap" 3) Fails with USE="fortran d" 4) Compiles with USE="-fortran d mudflap" My problem is that I need fortran for blas-atlas used by octave. Reproducible: Always Steps to Reproduce: 1. USE="fortran mudflap" emerge '=sys-devel/gcc-4.1.2' 2. Watch it fail on string-inst.lo (Log attatched) 3. USE="fortran d" emerge '=sys-devel/gcc-4.1.2' 4. Watch it fail on _conjg_c10.lo (Log attatched) Actual Results: Compiles fine when fortran is disabled Expected Results: To be able to have USE="fortran d mudflap" when compiling gcc-4.1.2 The logs are fairly large, so they're gzipped and attached. (Should this be filed upstream somehow?)
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! :-)
