Opened 8 years ago

Closed 8 years ago

#34907 closed defect (fixed)

Failed installation of gcc48 +gfortran breaks earlier gfortran builds

Reported by: rouson@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 2.1.1
Keywords: Cc: ryandesign (Ryan Schmidt), rouson@…
Port: gcc48

Description (last modified by ryandesign (Ryan Schmidt))

Attempting to install gcc48 +gfortran has somehow broken my earlier builds (and thereby brought all of my work to a halt). The trailing lines output from the build follow:

--->  Building gcc48
Error: for port gcc48 returned: command execution failed
To report a bug, follow the instructions in the guide:
Error: Processing of port gcc48 failed

After this, running gfortran on a simple one-line program produces the following ICE

$cat end.f90
$ gfortran-mp-4.7 end.f90 
dyld: Library not loaded: /opt/local/lib/libppl.9.dylib
  Referenced from: /opt/local/libexec/gcc/x86_64-apple-darwin10/4.7.0/f951
  Reason: image not found
gfortran-mp-4.7: internal compiler error: Trace/BPT trap (program f951)
Please submit a full bug report,
with preprocessed source if appropriate.
See <> for instructions.


Attachments (3)

main.log (35.2 KB) - added by rouson@… 8 years ago.
main.2.log (11.7 KB) - added by rouson@… 8 years ago.
gcc47 log
main.3.log (11.5 KB) - added by rouson@… 8 years ago.
gcc46 log

Download all attachments as: .zip

Change History (11)

comment:1 Changed 8 years ago by rouson@…

P.S. In case it helps, the aforementioned behavior happens on a machine with Snow Leopard (OS X 10.6.8). (I successfully built gcc48 +gfortran about two weeks ago on a machine with Lion.) Running "sudo port update outdated" fixes my gcc46 and gcc47 builds on my Snow Leopard machine. I'm hesitant to attempt a re-installation of gcc48 in case it breaks the gcc46 and gcc47 builds again. Any advice in this regard would be very much appreciative. There are new features in gfortran 4.8 that I'd like to access.

comment:2 Changed 8 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added
Description: modified (diff)
Owner: changed from macports-tickets@… to mww@…
Port: gcc48 added
Priority: HighNormal

You did not show it in your error message, but when gcc48 failed to install, it should have printed the location of gcc48's main.log file. (If it did not, you are using an outdated version of MacPorts and should upgrade to MacPorts 2.1.1 by using "sudo port selfupdate".) You should attach that log file to this ticket so that we can see why it failed. You can use the command "port logfile gcc48" to see where it is.

gcc48 depends on ppl, so if an update of ppl was available, MacPorts would have upgraded ppl first before trying to install gcc48. If that increased ppl's library version, you would now also need to rebuild any other ports that use ppl, such as gcc47. (On my system, the ppl port installed libppl.11.dylib, and no longer the older libppl.9.dylib that your gcc47 says it is expecting.) After running "sudo port selfupdate", use "port outdated" to see if gcc47 and any other ports have upgrades available; if so, upgrade them using "sudo port upgrade outdated".

comment:3 Changed 8 years ago by ryandesign (Ryan Schmidt)

Description: modified (diff)

comment:4 Changed 8 years ago by ryandesign (Ryan Schmidt)

P.S: In future, remember to use WikiFormatting when writing in Trac, and Cc the maintainer of the affected port so that he receives an email about your ticket and can begin to look into the problem.

comment:5 Changed 8 years ago by ryandesign (Ryan Schmidt)

Resolution: worksforme
Status: newclosed

No response from reporter; assuming updating outdated ports fixed the problem.

Changed 8 years ago by rouson@…

Attachment: main.log added

Changed 8 years ago by rouson@…

Attachment: main.2.log added

gcc47 log

Changed 8 years ago by rouson@…

Attachment: main.3.log added

gcc46 log

comment:6 Changed 8 years ago by rouson@…

Cc: rouson@… added

Cc Me!

comment:7 Changed 8 years ago by rouson@…

Resolution: worksforme
Status: closedreopened

I have now attached log files for gcc48, gcc47, and gcc46. All fail and now I'm stuck with no gcc on both a Snow Leopard and a Lion machine.

comment:8 Changed 8 years ago by mww@…

Resolution: fixed
Status: reopenedclosed

this problem is fixed in the latest revisions -- please update

Note: See TracTickets for help on using tickets.