libgcc processing fail - OSX 10.11

[sdstowe@…]

I recently upgraded to OSX 10.11 and have reinstalling/updating my ports, but I have ran into a wall with libgcc. I repeatly receive a processing error that aborts the installation that I cannot resolve. I have reinstalled XCode and Macports and reset both my PRAM and SMC, but the port still fails to complete its installation. Any suggestions?

[sdstowe@…]

log file for libgcc installation

[mf2k (Frank Schima)]

Please do not Cc openmaintainer@… because it is not a valid email address.

[macports@…]

I believe I'm having the same problem, and I think the key line both main.log's is:

    :info:build ld: symbol dyld_stub_binding_helper not found, normally in crt1.o/dylib1.o/bundle1.o for architecture x86_64

I was having this problem in 10.11. I've since upgraded to 10.11.1 which had some updates to XCode. Then I ran both port selfupdate and port upgrade outdated successfully. libgcc is used by py27-numpy (which I want) among other things.

[macports@…]

Cc Me!

[numeratus]

I've wiped/reinstalled macports, upgraded to 10.11.1, but still the same error

[macports@…]

What came out on the console.

[macports@…]

OS, Xcode & MacPorts versions, installed ports and versions.

[macports@…]

Good news everyone. More details in the macports_Capi_*_2015-10-30 attachments above.

I'm on Mac OS 11.1, Xcode 7.1 and MacPorts 2.3.4.

I did (suboptimal order, but it worked):

$ sudo port clean all
...
$ sudo port uninstall installed
...
$ port installed
No ports are installed.
$ sudo port install libgcc

It worked. Here is the list of ports I had when that finished:

$ port installed
The following ports are currently installed:
  cctools @870_0+llvm37 (active)
  dyld-headers @239.3_0 (active)
  expat @2.1.0_0 (active)
  gettext @0.19.6_0 (active)
  gmp @6.0.0_1 (active)
  gperf @3.0.4_2 (active)
  isl @0.14.1_0 (active)
  ld64 @2_0 (active)
  ld64-latest @253.3_0+llvm37 (active)
  libcxx @3.6.0_0 (active)
  libedit @20150325-3.1_0 (active)
  libffi @3.2.1_0 (active)
  libgcc @5.2.0_0 (active)
  libiconv @1.14_0 (active)
  libmacho-headers @870_0 (active)
  libmpc @1.0.3_0 (active)
  libunwind-headers @3.6.0_0 (active)
  llvm-3.7 @3.7.0_0 (active)
  llvm_select @1.0_0 (active)
  mpfr @3.1.3_0 (active)
  ncurses @6.0_0 (active)
  xz @5.2.2_0 (active)
  zlib @1.2.8_0 (active)
$

I was suspecting the version of ld64 I had used last week didn't handle the new .tbd files that El Capitan and Xcode 7 use. I don't seem to have saved last week's list of port versions, but maybe ld64-latest is more up-to-date this week. I do have a Time Machine backup from before clearing if anyone wants me to dig for the previous version number. I'm curious why I have two versions of ld64 after running just one port install command.

[numeratus]

Mac OS 10.11.1, Xcode 7.1 and MacPorts 2.3.4. I uninstalled everything, then tried installing libgcc before anything else, but ran into the same error as before (see main.3.log above).

[SickTeddyBear]

Cc Me!

[numeratus]

Replying to macports@…:

Mac OS 10.11.1, Xcode 7.1 and MacPorts 2.3.4. I uninstalled everything, then tried installing libgcc before anything else, but ran into the same error as before (see main.3.log above).

After a couple of months without being able to use the OS X Package installer on Yosemite, I installed macports from Subversion: ​https://guide.macports.org/#installing.macports.subversion

No problem since.

[ryandesign (Ryan Carsten Schmidt)]

Duplicate of #51789.