[MacPorts] #53144: libmacho @895 fails to build because GCC is not universal variant
MacPorts
noreply at macports.org
Sun Dec 25 02:08:14 CET 2016
#53144: libmacho @895 fails to build because GCC is not universal variant
------------------------+------------------------------
Reporter: ballapete | Owner: jeremyhu
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: fixed | Keywords: tiger, universal
Port: libmacho |
------------------------+------------------------------
Comment (by jeremyhu):
Replying to [comment:2 ballapete]:
> Replying to [comment:1 jeremyhu]:
> > In [changeset:"41e0ae1cf32e0a3d86283818c27e83e06fc8a853/macports-
ports" 41e0ae1c/macports-ports]:
> > {{{
> > #!ConfigurableCommitTicketReference repository="macports-ports"
revision="41e0ae1cf32e0a3d86283818c27e83e06fc8a853"
> > {apple,llvm}-gcc42: Default to +universal
> >
> > The build system basically conflates CHOST and CTARGET. This is
> > the simplest fix, and given the very deprecated nature of these
> > ports, it's not worth a deeper fix.
>
> What does that mean? I have no idea what a CHOST and a CTARGET could be…
That's the change log from the commit. It's not instructions for you.
CBUILD is the architecture of the system that is building the executable
CHOST is the architecture that the build executable will run on
CTARGET is the architecture that the build executable will generate code
for
> > Fixes https://trac.macports.org/ticket/53144
> >
>
> I seem to have a problem seeing the fix…
Just reinstall it +universal.
--
Ticket URL: <https://trac.macports.org/ticket/53144#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list