[MacPorts] #31777: openjade @1.3.2 clang fails, use llvm-gcc-4.2 instead, and also support +universal
MacPorts
noreply at macports.org
Tue Dec 20 23:57:03 PST 2011
#31777: openjade @1.3.2 clang fails, use llvm-gcc-4.2 instead, and also support
+universal
---------------------------+------------------------------------------------
Reporter: fgp@… | Owner: dports@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.0.3
Resolution: fixed | Keywords: clang universal haspatch
Port: openjade |
---------------------------+------------------------------------------------
Changes (by dports@…):
* status: assigned => closed
* resolution: => fixed
Comment:
Replying to [comment:7 ryandesign@…]:
> Patching libtool isn't so awful; we were already doing it in this port
(and in others of this vintage); now we'd just be patching it even better
to support `-arch` flags.
Yeah, I was hoping we could just replace it with a newer version of
libtool, but that's not looking like an easy task given some of the other
things that are going on with openjade's build system. Let's go with
patching libtool. Applied in r88165.
I was also thrown off by some linker errors that turned out to be caused
by openjade trying to link against libraries from an already-installed
version of itself. Fixed that in r88165 too. (It's possible that's the
problem I was seeing earlier and r88162 was unnecessary; testing that
now.)
--
Ticket URL: <https://trac.macports.org/ticket/31777#comment:8>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list