[MacPorts] #51832: libgcc command execution failed on macOS 10.12 Sierra
#51832: libgcc command execution failed on macOS 10.12 Sierra -------------------------------+-------------------------------- Reporter: stefan.meingast@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: Sierra | Port: libgcc -------------------------------+-------------------------------- I have been doing a clean install of macOS 10.12 (+ Xcode 8 beta 2) to check if any of my ports fail to build. The first one that fails is libgcc. I hope this log helps to clear up the issue before the final release in the Fall. -- Ticket URL: <https://trac.macports.org/ticket/51832> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc command execution failed on macOS 10.12 Sierra --------------------------------+-------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra Port: libgcc | --------------------------------+-------------------- Changes (by mf2k@…): * cc: stefan.meingast@… (removed) * keywords: Sierra => sierra * owner: macports-tickets@… => mww@… Comment: In the future, please Cc the port maintainers ({{{port info --maintainers libgcc}}}), if any. As reporter, you do not need to Cc yourself. -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc command execution failed on macOS 10.12 Sierra --------------------------------+-------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra Port: libgcc | --------------------------------+-------------------- Comment (by stefan.meingast@…): Replying to [comment:2 mf2k@…]:
In the future, please Cc the port maintainers ({{{port info --maintainers libgcc}}}), if any. As reporter, you do not need to Cc yourself.
Thanks, I will keep that in mind. Just started out submitting tickets here. :) -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc command execution failed on macOS 10.12 Sierra --------------------------------+-------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra Port: libgcc | --------------------------------+-------------------- Comment (by ethansherriff@…): I managed to get this building on Sierra with Xcode 8 beta 2 and the above patch. Please bear in mind this is only a workaround and don't sue me if it breaks your system :P -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc command execution failed on macOS 10.12 Sierra --------------------------------+-------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: sierra Port: libgcc | --------------------------------+-------------------- Comment (by stefan.meingast@…): Replying to [comment:5 ethansherriff@…]:
I managed to get this building on Sierra with Xcode 8 beta 2 and the above patch. Please bear in mind this is only a workaround and don't sue me if it breaks your system :P
Thanks! I had to revert to 10.11 for the moment since my testing computer (MacBook Pro late 2009) does not support 10.12 anymore and I depend on Macports (and gcc) for work. It would be great if you could try to build it with the latest beta versions of 10.12 and Xcode. -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Changes (by ryandesign@…): * keywords: sierra => * cc: jeremyhu@…, ryandesign@… (added) * port: libgcc => libgcc, libgcc-devel, cctools Comment: This issue is not Sierra-specific; I see it too with libgcc-devel on El Capitan, and it's the reason why I haven't updated the gcc7 port to the latest versions. I assume a recent update of cctools (the port that provides the `strip` program) is responsible for this. Jeremy, is this change intentional? If so, is the patch proposed in this ticket what we should do? -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by jeremyhu@…): Are you sure that it was a change between cctools-877.8 and cctools-886 that caused this? strip.c didn't change much between those two versions, and certainly not in a way that would manifest like this... -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by jeremyhu@…): Also, adding -i just tells strip to mask those errors. It's more likely that the error is in whatever is creating the object files not including whatever symbols you expect to be there. -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by ethansherriff@…): I know, that's why I said it's only a workaround :P. I'm willing to look more into this issue and come back with a better patch. -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by ryandesign@…): Replying to [comment:8 jeremyhu@…]:
Are you sure that it was a change between cctools-877.8 and cctools-886 that caused this? strip.c didn't change much between those two versions, and certainly not in a way that would manifest like this...
I have downgraded cctools from 886 to 877.8 and am re-trying the build of libgcc-devel @7-20160717 that failed for me before. It's been going for awhile now; I think it failed by now with cctools @886 but I'll report back later when it's done. -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by ryandesign@…): libgcc-devel succeeds with cctools 877.8. -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by jeremyhu@…): Ok, well then it's probably something else (not strip) that is the difference here. What variant are you using for cctools? I wonder if it's related to nm changing to llvm-nm when using llvm37 and higher. In such cases, if you change /opt/local/bin/nm to point to nm- classic instead of llvm-nm-mp-X.Y, does it work for you? -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:13> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by ryandesign@…): Replying to [comment:13 jeremyhu@…]:
What variant are you using for cctools?
+llvm37+universal
I wonder if it's related to nm changing to llvm-nm when using llvm37 and higher. In such cases, if you change /opt/local/bin/nm to point to nm- classic instead of llvm-nm-mp-X.Y, does it work for you?
Yes, that does work. -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:14> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by jeremyhu@…): Ok, so then the issue is a regression in llvm-nm compared to nm-classic (at least with llvm-3.7). We should check if the same issue still occurs with +llvm39 (and if not, determine if +llvm38 is impacted). I'll look through the log to see if there is an indication as to how they're invoking nm. -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:15> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by jeremyhu@…): {{{ :info:build llvm-nm: Unknown command line argument '-pg'. Try: '/opt/local/libexec/llvm-3.7/bin/llvm-nm -help' :info:build llvm-nm: Did you mean '-g'? }}} -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:16> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+------------------- Comment (by jeremyhu@…): 3.8 supports it but 3.7 doesn't. I'll update cctools to use nm-classic for +llvm37 -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:17> MacPorts <https://www.macports.org/> Ports system for OS X
#51832: libgcc, libgcc-devel: /opt/local/bin/strip: symbols names listed in: .../libgcc-darwin.10.4.ver not in: .../libgcc_s.dylib --------------------------------------------+-------------------- Reporter: stefan.meingast@… | Owner: mww@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: libgcc, libgcc-devel, cctools | --------------------------------------------+-------------------- Changes (by jeremyhu@…): * status: new => closed * resolution: => fixed Comment: r150633 -- Ticket URL: <https://trac.macports.org/ticket/51832#comment:18> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts