Opened 9 years ago

Closed 9 years ago

#49300 closed defect (worksforme)

port upgrade ld64-latest fails

Reported by: persramd@… Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: McDutchie (Martijn Dekker)
Port: ld64-latest

Description (last modified by mf2k (Frank Schima))

I was just recently able to selfupdate after the recent problem with signature verification (49233)

port upgrade outdated failed on ld64-latest.

So I did a port clean ld64-latest, followed by

port upgrade ld64-latest

fails.

declan@nona:~$ sudo port upgrade ld64-latest
--->  Computing dependencies for ld64-latest
--->  Building ld64-latest
Error: org.macports.build for port ld64-latest returned: command execution failed
Please see the log file for port ld64-latest for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64-latest/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets


Attachments (1)

main.log (31.8 KB) - added by persramd@… 9 years ago.
log file

Download all attachments as: .zip

Change History (11)

Changed 9 years ago by persramd@…

Attachment: main.log added

log file

comment:1 Changed 9 years ago by mf2k (Frank Schima)

Owner: changed from macports-tickets@… to jeremyhu@…
Port: ld64-latest added

In the future, please fill in the Port field and Cc the port maintainers (port info --maintainers ld64-latest), if any.

comment:2 Changed 9 years ago by mf2k (Frank Schima)

Description: modified (diff)

comment:3 Changed 9 years ago by McDutchie (Martijn Dekker)

Cc: martijn@… added

Cc Me!

comment:4 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)

What version of Xcode do you have? Are your CLTools up to date with it? What's the output of:

/usr/bin/clang++ --version

comment:5 in reply to:  4 Changed 9 years ago by persramd@…

Replying to jeremyhu@…:

What version of Xcode do you have? Are your CLTools up to date with it? What's the output of:

/usr/bin/clang++ --version

Xcode: Version 4.6.3 (4H1503)

declan@nona:~$ /usr/bin/clang++ --version
Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.2
Thread model: posix
declan@nona:~$ 
Last edited 9 years ago by persramd@… (previous) (diff)

comment:6 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Your command line tools are out of date. Your CLTools are from Xcode 4.4. If you update them, does the issue go away?

comment:7 in reply to:  6 Changed 9 years ago by persramd@…

Replying to jeremyhu@…:

Your command line tools are out of date. Your CLTools are from Xcode 4.4. If you update them, does the issue go away?

4.6.3 is the most up-to-date version for OSX 10.7.5. Might there be a workaround?

comment:8 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Your version of Xcode is 4.6.3, but the version of the CLTools is from Xcode 4.4. You have not updated your CLTools to the 4.6.3 version. Please update your CLTools to 4.6.3.

comment:9 Changed 9 years ago by p.ohanlon@…

In my case updating to CLTools 4.6.3 did address the problem. The catch was that when I installed the Command line tools with Xcode 4.6.3 they were installed into /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ and not into /usr/bin (possibly because I kept an older version installed there). Anyway I renamed the old versions of clang,clang++ and softlinked the new ones in its place, after which ld64 built ok.

In case anyone else finds it useful I used the xcrun command to find clang's location:

$ xcrun --find clang
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang

comment:10 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: worksforme
Status: newclosed

Thanks for confirming.

Note: See TracTickets for help on using tickets.