[MacPorts] #57243: atom @1.30.0 fails to build on Mojave: linking against libstdc++ fails
MacPorts
noreply at macports.org
Thu Oct 25 15:44:20 UTC 2018
#57243: atom @1.30.0 fails to build on Mojave: linking against libstdc++ fails
--------------------------+----------------------------
Reporter: michaellass | Owner: kurthindenburg
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: fixed | Keywords: mojave
Port: atom |
--------------------------+----------------------------
Comment (by michaellass):
Replying to [comment:7 kencu]:
> I don't completely understand what's going on with this fix, but it
looked a bit strange and I deleted it out of the Portfile, and `atom`
built for me right through on Mojave with Xcode10. Perhaps some piece of
atom was updated since the original report? At any rate, this might be
looked at again at some time in the future to see if it is really needed
any longer, as it does not seem to be needed for me.
Indeed the issue is magically gone with Atom 1.31.2. I can still reproduce
it with 1.30.0 so there must be a change between these versions fixing it.
Tracing this down is not worth the effort since many nodejs packages are
built during installation and the output is not very verbose. I don't even
know which one of those caused the issue in the first place.
So I guess we can just drop the workaround again. Here's a pull request:
https://github.com/macports/macports-ports/pull/2874
--
Ticket URL: <https://trac.macports.org/ticket/57243#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list