libgcc port missing

[da.hoffman.pb@…]

This is the error message:

--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  Found 1 broken file(s), matching files to ports
--->  Found 1 broken port(s), determining rebuild order
--->  Rebuilding in order
     py27-scipy @0.12.0 +gcc47
--->  Computing dependencies for py27-scipy
Error: Dependency 'libgcc' not found.
Error: Unable to upgrade port: 1
Error rebuilding py27-scipy
    while executing
"error "Error rebuilding $portname""
    (procedure "revupgrade_scanandrebuild" line 382)
    invoked from within
"revupgrade_scanandrebuild broken_port_counts $opts"
    (procedure "macports::revupgrade" line 5)
    invoked from within
"macports::revupgrade $opts"
    (procedure "action_revupgrade" line 2)
    invoked from within
"action_revupgrade $action $portlist $opts"
    (procedure "action_target" line 94)
    invoked from within
"$action_proc $action $portlist [array get global_options]"
    (procedure "process_cmd" line 95)
    invoked from within
"process_cmd $remaining_args"
    invoked from within
"if { [llength $remaining_args] > 0 } {

    # If there are remaining arguments, process those as a command
    set exit_status [process_cmd $remaining..."
    (file "/opt/local/bin/port" line 4785)

I tried to upgrade py27-scipy and that failed because of a missing 'db48'. Two weeks ago I tried to install Julia, and that failed. Three attempts and three failure in two weeks on two different computers. Should I switch to HomeBrew?

[larryv (Lawrence Velázquez)]

Replying to da.hoffman.pb@…:

--->  Rebuilding in order
     py27-scipy @0.12.0 +gcc47
--->  Computing dependencies for py27-scipy
Error: Dependency 'libgcc' not found.

This is strange. What does sudo port selfupdate && port info libgcc return?

I tried to upgrade py27-scipy and that failed because of a missing 'db48'.

Sounds like it could be related to your missing libgcc.

Two weeks ago I tried to install Julia, and that failed.

Did you file a ticket for this?

[ryandesign (Ryan Carsten Schmidt)]

This problem is unique to your system, so we need to figure out what is happening on your system.

Try running selfupdate with the debug flag, in case something is going wrong there:

sudo port -d selfupdate

[larryv (Lawrence Velázquez)]

Reposting OP’s email response from ~10 hours ago (formatted for Trac):

I am new to the trac system; this is my second attempt to reply.

No, I did not file a ticket on the Julia problem (I was using a laptop running Mavericks). It involved a hang while "staging to destroot", and nobody other than me was complaining about it (according to Google). I cannot run port selfupdate because I am behind a firewall (I used "port sync" instead, and I doing this was my first response to this error. When I run "port info libgcc" I get another error message:

$  port info libgcc 
Error: Port libgcc not found

when I run "port installed | grep gcc" produces

$  port installed | grep "gcc"
  gcc43 @4.3.6_7 (active)
  gcc47 @4.7.3_1 (active)
  gcc_select @0.1_8 (active)
  py27-scipy @0.12.0_2+gcc47 (active)

I would think that having GCC would imply having libgcc (should only one GCC be active at any time?). Thank you for your fast response. Sorry for my earlier irritation.

[da.hoffman.pb@…]

This is strange. What does sudo port selfupdate && port info libgcc return?

I ran port -d sync, and it returned quite a lot. I hope it fits:

[log moved to attachment:sync.log​ by admin]

Sorry about the lack of line feeds.

David

[larryv (Lawrence Velázquez)]

Replying to da.hoffman.pb@…:

I ran port -d sync, and it returned quite a lot. I hope it fits:

It’s best to provide long pieces of text as attachments instead of pasting them inline. The “Attach file” button is just below the ticket description.

Failed to parse file aqua/qt5-mac/Portfile: invalid command name "configure.cxx_stdlib"

The configure.cxx_stdlib option (and several others listed in your output) have been supported in MacPorts releases for quite some time. This suggests that your base installation is significantly out of date, which is unsurprising given that you use port sync instead of port selfupdate. (port sync only updates your ports tree, while port selfupdate updates MacPorts base also.)

The simplest remedy is to download and run the latest installer package to get the latest MacPorts. This won’t touch your installed ports.

Sorry about the lack of line feeds.

FYI, Trac lets you use WikiFormatting to format code blocks and such.

[ryandesign (Ryan Carsten Schmidt)]

Replying to da.hoffman.pb@…:

I cannot run port selfupdate because I am behind a firewall

You need to update MacPorts base; as Larry said, the problem you are experiencing is because your ports collection is using features that your old version of MacPorts does not support. We do not support running versions of MacPorts older than the current version. Since you cannot use selfupdate, you must update another way, for example by downloading the installer package on our web site and running it.

I would think that having GCC would imply having libgcc

That should be the case, yes. It's apparently not on your system, but your system is not in a supported state, so please update base, then upgrade outdated ports, to hopefully get your system back to a supported state.

(should only one GCC be active at any time?).

You are welcome to have any number of gcc ports installed and active at once. They can coexist without problems.

[ryandesign (Ryan Carsten Schmidt)]

So, this is not a bug. If you need further help resolving the issue, please write to the macports-users mailing list.