#37463: llvm-3.2 does not build / universal variants semantics should be changed -----------------------+----------------------- Reporter: vince@… | Owner: jeremyhu Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: universal Port: llvm-3.2 | -----------------------+----------------------- Comment (by jeremyhu@…): Replying to [ticket:37463 vince@…]:
When building llvm-3.2 I get this error:
Attach main.log
Besides, the ‘universal’ variant should not mean building a universal compiler, but building a compiler than can compile for both i386/x86-64, which is the default case. The classical meaning of ‘universal’ should be transferred to some other variant.
No. +universal means that the built binaries will run on either machine. This is true for *all* ports. Making it have a different meaning (ie CTARGET rather than CHOST) for toolchain ports is nonsensical. Furthermore, there is no reason to care about CTARGET for llvm because it is not as restricted as gcc and can support multiple targets with the same build. -- Ticket URL: <https://trac.macports.org/ticket/37463#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS