Opened 12 years ago
Closed 12 years ago
#34834 closed defect (invalid)
llvm-3.0: automatic rebuild via rev-upgrade fails with 'Undefined symbols for architecture x86_64: "_LLVMInitializeARMDisassembler"'
Reported by: | lpsinger (Leo Singer) | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.1 |
Keywords: | Cc: | ||
Port: | llvm-3.0 |
Description
An automatic rebuild of llvm-3.0 triggered by an upgrade of libffi from libffi @3.0.10_2+universal
to libffi @3.0.10_2+universal
fails on my OS X Lion machine. The relevant part of the (attached) build log appears to be:
:info:build ld: warning: ignoring file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.0/llvm-3.0/work/llvm-3.0.src/Release+Debug/lib/libLLVMARMDisassembler.a, file was built for archive which is not the architecture being linked (x86_64) :info:build Undefined symbols for architecture x86_64: :info:build "_LLVMInitializeARMDisassembler", referenced from: :info:build _LLVMCreateDisasm in libLLVMMCDisassembler.a(Disassembler.o) :info:build llvm::EDDisassembler::initialize() in libLLVMMCDisassembler.a(EDDisassembler.o) :info:build ld: symbol(s) not found for architecture x86_64 :info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)
Attachments (1)
Change History (6)
Changed 12 years ago by lpsinger (Leo Singer)
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to jeremyhu@… |
---|
comment:2 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)
comment:3 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)
And I *just* rebuilt it due to the same libffi issue.
comment:4 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Any further info? I can't reproduce your failure...
comment:5 Changed 12 years ago by lpsinger (Leo Singer)
Resolution: | → invalid |
---|---|
Status: | new → closed |
No; the issue went away on its own.
Note: See
TracTickets for help on using
tickets.
Works for me...