[MacPorts] #54773: port:libgcc/port:gcc7: proposed modifications, efficiency + libc++ support
MacPorts
noreply at macports.org
Mon Sep 11 18:35:57 UTC 2017
#54773: port:libgcc/port:gcc7: proposed modifications, efficiency + libc++ support
--------------------------+----------------------
Reporter: RJVB | Owner:
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords: haspatch
Port: gcc7 libgcc |
--------------------------+----------------------
Comment (by jeremyhu):
Replying to [comment:13 RJVB]:
> Replying to [comment:12 jeremyhu]:
> > > is there a hard reason why I shouldn't simply use /usr/bin/as -q
> >
> > Because that will only work well on Xcode 7 or 8 and newer.
>
> Care to give a bit more detail?
> My Xcode 6.something packs a clang 3.5 version and by the time you get
around to replying I should have confirmation if gcc itself builds using
that version for assembler or not.
Ok, then maybe it is for Xcode 6 and newer. In any event, this
functionality is pretty recent and definitely won't work with older tools.
> > Newer compiler runtime functionality was available on 10.4 and 10.5.
Those dylibs cause that functionality to be packed up by "our"
libgcc_s.1.dylib given that it is not present on the host OS.
>
> Which is the earliest OS version this port builds on as it is currently
anyway?
That question is not relevant here. You are confusing the version of the
OS that you are running on versus the version of the OS that you are using
the tools to build for. These libraries are used when using a deployment
target older than 10.6 (even when building on much newer OS versions).
--
Ticket URL: <https://trac.macports.org/ticket/54773#comment:15>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list