Opened 9 years ago
Closed 9 years ago
#48163 closed defect (wontfix)
clang-3.6 @3.6.1_1: incorrectly uses libunwind port if installed
Reported by: | mkae (Marko Käning) | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | larryv (Lawrence Velázquez) | |
Port: | clang-3.6 |
Description
What's going on with libunwind
and the architectures here?
:info:build /opt/local/bin/ranlib 2> /dev/null /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build/tools/clang/ runtime/compiler-rt/clang_darwin/ubsan_osx/i386/libcompiler_rt.a :info:build /opt/local/bin/ranlib 2> /dev/null /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build/tools/clang/ runtime/compiler-rt/clang_darwin/ubsan_osx/x86_64/libcompiler_rt.a :info:build ld: in '/opt/local/lib/libunwind.dylib', file was built for x86_64 which is not the architecture being linked (i386): /opt/local/lib/libunwind.dylib for architecture i386 :info:build clang: error: linker command failed with exit code 1 (use -v to see invocation) :info:build make[4]: *** [/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build/tools/clang/runtime/compiler-rt/ clang_darwin/asan_osx_dynamic/i386/libcompiler_rt.dylib] Error 1 :info:build make[4]: *** Waiting for unfinished jobs.... :info:build make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/llvm-3.6.1.src/projects/ compiler-rt' :info:build make[3]: *** [BuildRuntimeLibraries] Error 2 :info:build rm /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build/Release+Debug/lib/clang/3.6.1/lib/darwin/.dir / opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build/Release+Debug/lib/clang/3.6.1/lib/macho_embedded/.dir :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build/tools/clang/runtime/ compiler-rt' :info:build make[2]: *** [compiler-rt/.makeall] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build/tools/clang/runtime' :info:build make[1]: *** [all] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build/tools/clang' :info:build make: *** [all] Error 1 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.6/clang-3.6/work/build" && /usr/bin/make -j5 -w clang-only :info:build Exit code: 2 :error:build org.macports.build for port clang-3.6 returned: command execution failed
Change History (11)
comment:1 Changed 9 years ago by larryv (Lawrence Velázquez)
Summary: | clang-3.6 @3.6.1_1: fails to build on Mavericks → clang-3.6 @3.6.1_1: incorrectly uses libunwind port if installed |
---|
comment:2 Changed 9 years ago by mkae (Marko Käning)
Can one forbid that for clang in its portfile somehow, or do I need to manually deactivate it myself before upgrading clang?
comment:3 Changed 9 years ago by mkae (Marko Käning)
I've uninstalled port libunwind
and upgraded clang-3.6
successfully by now.
comment:4 follow-up: 5 Changed 9 years ago by mkae (Marko Käning)
So, shall this be
- considered a port bug to be fixed (perhaps by simply adding a warning ui_msg?)
- or closed as invalid?
comment:5 Changed 9 years ago by larryv (Lawrence Velázquez)
Leave it open. The opportunistic nature makes it a port bug.
comment:6 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Yeah, we need to fix this. Don't close it.
comment:7 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Can you please attach your full log?
comment:8 Changed 9 years ago by mkae (Marko Käning)
Sorry, that's already history. I can't supply a log anymore without reverting to the previous clang-3.6 version, reinstalling libunwind and redoing a clang-3.6 update.
comment:9 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Ok, well from what I can tell, the i386 ASan libcompiler_rt.dylib build tried to link against MacPorts' libunwind.dylib for some reason. I'll need to take a closer look at the Makefiles. Did clang-3.5 and/or clang-3.7 build ok for you with libunwind installed?
comment:10 Changed 9 years ago by mkae (Marko Käning)
I _believe_ that clang-3.5 didn't misbehave. clang-3.7 I didn't have installed at the time, sorry.
comment:11 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
This is an issue with the linker and no w something we can really do anything about. You should install libunwind +universal.
You have the
libunwind
port installed? It looks like Clang’s build is picking that up accidentally.