Opened 11 years ago
Closed 11 years ago
#40758 closed defect (fixed)
ld64 @136_2 Build error under Mavericks
Reported by: | panayotis@… | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.0 |
Keywords: | Cc: | help@…, ldalessandro@… | |
Port: | ld64 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I am trying to use some packages depending on ld64, but it seems to have some issues.
# port clean ld64 ---> Cleaning ld64 root@temp2:/opt/local/var/macports/sources/rsync.macports.org/release/tarballs# port install ld64 ---> Computing dependencies for ld64 ---> Fetching archive for ld64 ---> Attempting to fetch ld64-136_2+llvm33.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/ld64 ---> Attempting to fetch ld64-136_2+llvm33.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ld64 ---> Attempting to fetch ld64-136_2+llvm33.darwin_13.x86_64.tbz2 from http://packages.macports.org/ld64 ---> Fetching distfiles for ld64 ---> Verifying checksums for ld64 ---> Extracting ld64 ---> Applying patches to ld64 ---> Configuring ld64 ---> Building ld64 Error: org.macports.build for port ld64 returned: command execution failed Please see the log file for port ld64 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ld64 failed
Attachments (2)
Change History (15)
Changed 11 years ago by panayotis@…
comment:1 Changed 11 years ago by mattbrocklehurst@…
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to jeremyhu@… |
comment:6 follow-up: 8 Changed 11 years ago by help@…
For me this error occurs when macosx_deployment_target is set in macports.conf to any value < 10.9. When unset or set to 10.9 compile succeeds.
comment:8 Changed 11 years ago by ldalessandro@…
Replying to help@…:
For me this error occurs when macosx_deployment_target is set in macports.conf to any value < 10.9. When unset or set to 10.9 compile succeeds.
I just upgraded to Mavericks today, and I'm desperately trying to get this installed because it blocks absolutely every port that I use.
I don't see macosx_deployment_target in /opt/local/etc/macports/macports.conf. I tried adding it set to 10.9, but that doesn't help either. Can you elaborate on how you got this to work?
comment:9 follow-up: 10 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Make sure you reinstall the command line tools after upgrading to 10.9.
comment:10 Changed 11 years ago by ldalessandro@…
Replying to jeremyhu@…:
Make sure you reinstall the command line tools after upgrading to 10.9.
I did, and had accepted the license. This didn't work. I did a complete clean and uninstall of macports, and that didn't help either. I then installed the full xcode app from the app store and reinstalled macports, and this fixed my problem. I have no idea what the difference between the full xcode app and the command line tools is.
Thank you for the work you put into maintaining this port.
comment:11 Changed 11 years ago by mf2k (Frank Schima)
Trac is not for tech support. Use the Macports Users mailing list instead.
comment:12 Changed 11 years ago by help@…
Resolution: | invalid |
---|---|
Status: | closed → reopened |
While installing command line tools may have helped original reporter, ld64 is still broken for me when macosx_deployment_target is used. I've attached my log. Command line tools and Xcode are installed.
comment:13 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
New issues require new tickets.
Missing include file
Think this is something to do with switching compilers on Mavericks from Gcc to lvmm