Opened 13 years ago
Closed 10 years ago
#30479 closed defect (duplicate)
gcc45 installation fails: seems to be related to fortran
Reported by: | philip@… | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.0 |
Keywords: | Cc: | ||
Port: | gcc45 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
This fails on fully patched (including xcode) 10.6 on an i7 4 core MBP, default installation of MacPorts:
sudo port install -d gcc45
The only irregularity I'm aware of is commenting out the LLVM check in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/gmp to enable it to build (this is a suggested work-around).
looking at logs, it seems to fall over here:
/usr/bin/make -j5 -w bootstrap
here's where it seems to realise it's gone wrong:
checking whether the GNU Fortran compiler is working... no 783 configure: error: GNU Fortran is not working; please report a bug in http://gcc.gnu.org/bugzilla, attaching /opt/local/var/macports /build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc45/gcc45/work/build/x86_64-apple-darwin10/ libgfortran/config.log
Attachments (1)
Change History (7)
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to mww@… |
Changed 13 years ago by philip@…
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc45/gcc45/main.log
comment:2 follow-up: 5 Changed 13 years ago by jmroot (Joshua Root)
The attached log starts with the build phase already partly complete. Please clean and generate a complete log.
comment:3 follow-up: 4 Changed 13 years ago by jmroot (Joshua Root)
Also check if this happens with an unmodified gmp; the check for llvm-gcc is there for a reason.
comment:4 Changed 13 years ago by philip@…
Replying to jmr@…:
Also check if this happens with an unmodified gmp; the check for llvm-gcc is there for a reason.
The gmp was modified in order to get it to build at all... the unmodified gmp wouldn't build.
comment:5 Changed 13 years ago by philip@…
Replying to jmr@…:
The attached log starts with the build phase already partly complete. Please clean and generate a complete log.
Hi jmr. Thanks for looking at this. You may have noticed that the bug was posted about 9 months ago. Since then I've moved machines twice. The main one I'm on is on 10.7 - so reproducing this could be a problem. If I recall, I ended up building gcc45 using source obtained directly from the gcc site - it wasn't convenient nor pretty, but it got the job done. As general note, various mac port problems I've had in the past seemed to be fixed by doing port builds using a clean user. I have never managed to figure out what it is about my user account (my .profile and .bashrc files are trivially simple) is causing the problem - is there a known profile leakage/sensitivity issue?
comment:6 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | gcc gcc45 fortran removed |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
No, the problems you describe regarding user accounts are completely unfamiliar to me.
The error shown in the attached log ("configure: error: GNU Fortran is not working; please report a bug
") is familiar and is tracked in #40548.
Please attach the entire main.log and/or report this bug to the developers of gcc as the error message stated.