#35784 closed defect (fixed)
clang-3.2 build fails complaining "can't be weak reference"
| Reported by: | yaseppochi (Stephen J. Turnbull) | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.2 |
| Keywords: | Cc: | deesto (John S. De Stefano Jr.), pixilla (Bradley Giesbrecht) | |
| Port: | clang-3.2 |
Description
Mac OS X 10.6.8 2.7 GHz Intel Core i7
Attachments (3)
Change History (12)
Changed 12 years ago by yaseppochi (Stephen J. Turnbull)
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to jeremyhu@… |
|---|
Changed 12 years ago by deesto (John S. De Stefano Jr.)
| Attachment: | clang-3.2.log added |
|---|
Another upgrade log.
comment:3 Changed 12 years ago by deesto (John S. De Stefano Jr.)
My log attached, also on 10.6.8, with "can't be a weak_definition" error.
comment:6 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:7 Changed 12 years ago by deesto (John S. De Stefano Jr.)
A patch was proposed, but not yet verified. And I can't get the port to build after applying the proposed patch to the current code base fails (the patch file itself fails, but it's simple enough to apply the changes manually). Perhaps I'm patching the wrong file:
/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_lang_clang-3.2/clang-3.2/work/trunk/tools/clang/tools/clang-check/ClangCheck.cpp
... or not properly attempting to build the port:
sudo port build clang-3.2
comment:8 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)
deetso, the changes are committed. You should just port sync and install it...
Changed 12 years ago by deesto (John S. De Stefano Jr.)
| Attachment: | clang-3.2-build-error.log added |
|---|
Log of another clang-3.2 upgrade attempt from after the code change.
comment:9 Changed 12 years ago by deesto (John S. De Stefano Jr.)
This is a completely different and unrelated error that you're seeing now:
ld: -L must be immediately followed by a directory path (no space) clang: error: linker command failed with exit code 1 (use -v to see invocation)
Can you figure out what is being passed to the linker?
No, but if you have any ideas on how to gather that information, I'll be glad to give it a try?
log of port -u upgrade