#49258: libgcc processing fail - OSX 10.11 ------------------------+------------------- Reporter: sdstowe@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc | ------------------------+------------------- Comment (by 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. -- Ticket URL: <https://trac.macports.org/ticket/49258#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X