#30479: gcc45 installation fails: seems to be related to fortran --------------------------------------+------------------------------------- Reporter: philip@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Keywords: gcc gcc45 fortran | Port: gcc45 --------------------------------------+------------------------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => mww@… Old description:

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''

New description: 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 }}} -- Comment: Please attach the entire main.log and/or report this bug to the developers of gcc as the error message stated. -- Ticket URL: <https://trac.macports.org/ticket/30479#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30479: gcc45 installation fails: seems to be related to fortran --------------------------------------+------------------------------------- Reporter: philip@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Keywords: gcc gcc45 fortran | Port: gcc45 --------------------------------------+------------------------------------- Comment(by jmr@…): Also check if this happens with an unmodified gmp; the check for llvm-gcc is there for a reason. -- Ticket URL: <https://trac.macports.org/ticket/30479#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#30479: gcc45 installation fails: seems to be related to fortran --------------------------------------+------------------------------------- Reporter: philip@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.0 Keywords: gcc gcc45 fortran | Port: gcc45 --------------------------------------+------------------------------------- Comment(by philip@…): Replying to [comment:2 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?

-- Ticket URL: <https://trac.macports.org/ticket/30479#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS