#38177: clang-3.2 builds parts universal when not asked to --------------------------+------------------------ Reporter: ryandesign@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: clang-3.2 --------------------------+------------------------ Parts of clang-3.2 are universal, even though I am not using the universal variant: {{{ $ lipo -info /opt/local/libexec/llvm-3.2/bin/ld Architectures in the fat file: /opt/local/libexec/llvm-3.2/bin/ld are: i386 x86_64 $ port provides /opt/local/libexec/llvm-3.2/bin/ld /opt/local/libexec/llvm-3.2/bin/ld is provided by: clang-3.2 $ port -v installed clang-3.2 llvm-3.2 The following ports are currently installed: clang-3.2 @3.2_0+analyzer+python27 (active) platform='darwin 9' archs='i386' llvm-3.2 @3.2_0 (active) platform='darwin 9' archs='i386' $ }}} This is a problem on x86_64 Leopard machines, because while i386 is the default build_arch, if an x86_64 part is in a binary, it will be used. What happens is that actually trying to use clang-3.2 to build another port fails: {{{ dyld: Library not loaded: @executable_path/../lib/libLTO.dylib Referenced from: /opt/local/libexec/llvm-3.2/bin/ld Reason: no suitable image found. Did find: /opt/local/libexec/llvm-3.2/bin/../lib/libLTO.dylib: mach-o, but wrong architecture clang: error: unable to execute command: Trace/BPT trap clang: error: linker command failed due to signal (use -v to see invocation) }}} I only tested the clang-3.2 port; the other versions are probably affected too. -- Ticket URL: <https://trac.macports.org/ticket/38177> MacPorts <http://www.macports.org/> Ports system for Mac OS