git-core @1.8.2.2 install fail

[bcptaylor@…]

This is a new development MacBook Pro (work) with fresh 10.8.3, macports version 2.1.3 I tried upgrading installed ports, git-core failed with error like:

  Error: org.macports.build for port git-core returned: command execution failed

I tried the advice on uninstalling/cleaning, same error. I followed the advice on wiki:ProblemHotlist regarding the Xcode tools (using apple-gcc42) also failed.

New installs always fail now with the same error as above.

[bcptaylor@…]

compile log with llvm gcc42

[bcptaylor@…]

compile log with apple gcc42

[bcptaylor@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

git-core should have built with clang, since it does not specify any compiler blacklisting. I suspect your command line tools are very out of date, because (as part of checking git-core's dependency gettext, which does use compiler blacklisting) the log says:

:debug:main compiler clang 163.7.1 blacklisted because matches {clang < 211.10.1}

clang 163.7.1 was included with Xcode 4.1.0, but OS X 10.8 requires Xcode 4.4 or later. Please ensure you have at least Xcode 4.4, preferably the latest version 4.6.2, which you can get either from the Mac App Store or Apple Developer Connection. Then, open Xcode.app, go to the Preferences window, to the Downloads section, and install or update the command line tools. Then clean git-core (sudo port clean git-core) and re-try your attempt to install it.

You also mentioned that this is a "new development MacBook Pro" with a "fresh 10.8.3", but then you mentioned "upgrading installed ports". If you just upgraded to OS X 10.8, or used Migration Assistant to transfer an old MacPorts installation from a pre-10.8 Mac, read wiki:Migration for additional required steps.

[bcptaylor@…]

Thanks Ryan. I have Xcode 4.6.2 installed, from app store, with command line tools. I wiped this macbook clean (disk util erased) when I got it, installed 10.8 clean from recovery partition. After a week I ran the update command, which is when git-core failed.

I ran the clean command, and the install with no compiler specified. It failed with the same error, and I've attached the result.

Thank you very much for macports and your support.

[bcptaylor@…]

install with default compiler

[larryv (Lawrence Velázquez)]

Replying to bcptaylor@…:

Thanks Ryan. I have Xcode 4.6.2 installed, from app store, with command line tools.

Can you run this and provide the output?

% /usr/bin/clang --version

[ci42]

Replying to bcptaylor@…:

Thanks Ryan. I have Xcode 4.6.2 installed, from app store, with command line tools.

The log file still says:

:debug:main compiler clang 163.7.1 blacklisted because matches {clang < 211.10.1} 

What's the output of:

$ xcode-select -print-path

and:

$ xcodebuild -version

?

[bcptaylor@…]

Thanks! Here is the info requested

$ /usr/bin/clang --version
Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

$ xcode-select -print-path
/Applications/Xcode.app/Contents/Developer

$ xcodebuild -version
Xcode 4.6.2
Build version 4H1003

[larryv (Lawrence Velázquez)]

Replying to bcptaylor@…:

$ /usr/bin/clang --version
Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

This is completely wrong. Xcode 4.6.2 comes with a much newer Clang.

% xcodebuild -version
Xcode 4.6.2
Build version 4H1003
% /usr/bin/clang --version
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

Are you sure you can’t install or update the Command Line Tools from Xcode (Xcode menu > Preferences > Downloads > Components)?

[bcptaylor@…]

It sounds like my installation is somehow borked, but I don't know how. I appreciate the help, as I have no idea where to look. But seeing as it is seemingly not a port defect, I understand if you want to close the ticket. I've attached a screen capture of the Xcode preferences showing the command line tools version...it shows 4.6.2 4H1003. I don't know enough to understand why the command line clang shows one version but the xcode prefs show another. I welcome suggestions if possible...thank you for all your help.

[bcptaylor@…]

Xcode preferences screen capture

[ci42]

Replying to bcptaylor@…:

It sounds like my installation is somehow borked, but I don't know how. I appreciate the help, as I have no idea where to look. But seeing as it is seemingly not a port defect, I understand if you want to close the ticket. I've attached a screen capture of the Xcode preferences showing the command line tools version...it shows 4.6.2 4H1003. I don't know enough to understand why the command line clang shows one version but the xcode prefs show another. I welcome suggestions if possible...thank you for all your help.

Do you have another clang in your path? Could you please check:

$ which clang
$ clang --version

And check the clang version of your Xcode installation:

$ xcodebuild -find clang
$ `xcodebuild -find clang` --version

[bcptaylor@…]

Only /usr/bin/clang is in path. I ran find on / to find all executable clangs, the only ones were the /usr/bin/clang and the /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang

$ which clang
/usr/bin/clang
$ hash -t clang
/usr/bin/clang

$ /usr/bin/clang --version
Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

$ `xcodebuild -find clang` --version
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

[ci42]

Replying to bcptaylor@…:

Only /usr/bin/clang is in path. I ran find on / to find all executable clangs, the only ones were the /usr/bin/clang and the /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang

$ /usr/bin/clang --version
Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

Ok, could you please run:

$ pkgutil --file-info /usr/bin/clang

and provide the output.

[bcptaylor@…]

Sure, thank you for all the help.

Output attached.

[bcptaylor@…]

output of pkgutil

[ryandesign (Ryan Carsten Schmidt)]

The output shows that at 1366911490 (a.k.a. Thu Apr 25 12:38:10 CDT 2013) you installed com.apple.pkg.DeveloperToolsCLI 4.6.0.0.1.1365549073 (a.k.a. Xcode 4.6's command line tools) but then at 1366996353 (a.k.a. Fri Apr 26 12:12:33 CDT 2013) you installed com.apple.pkg.clangLeo 1.0.0.9000000000.1.1249367152 (a.k.a. Xcode 4.1's command line tools).

[ryandesign (Ryan Carsten Schmidt)]

You could probably fix this by downloading and installing "Command Line Tools (OS X Mountain Lion) for Xcode - April 2013" from ​http://connect.apple.com/

[bcptaylor@…]

Wow you guys are awesome. That definitely worked. Thank you so much for your perseverance and expertise. I definitely would not have been able to solve this on my own.

$ clang --version
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.3.0
Thread model: posix

$ sudo port install git-core
Password:
--->  Computing dependencies for git-core
--->  Building git-core
--->  Staging git-core into destroot
--->  Installing git-core @1.8.2.2_0+credential_osxkeychain+doc+pcre+python27
--->  Activating git-core @1.8.2.2_0+credential_osxkeychain+doc+pcre+python27
--->  Cleaning git-core
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.

[larryv (Lawrence Velázquez)]

Glad you’ve got everything working.