GitX @0.7.1 build failure

[larryv@…]

I uninstalled GitX prior to installing git-core @1.7.3.3 -bash_completion +doc +python27 +svn. (Probably didn’t have to, but MacPorts was bugging me about the dependency, and this was the path of least resistance.) After successfully updating git-core, I attempted to reinstall GitX, which failed at the build phase:

% sudo port install gitx
--->  Computing dependencies for GitX
...
--->  Building GitX
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for GitX is at: /opt/local/var/macports/logs/<blah>/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

The end of the install log says:

:info:build ** BUILD FAILED **
:info:build 
:info:build 
:info:build The following build commands failed:
:info:build cli tool:
:info:build 	CompileC "build/GitX.build/Release/cli tool.build/Objects-normal/x86_64/PBEasyPipe.o" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_GitX/work/GitX-0.7.1/PBEasyPipe.m normal x86_64 objective-c com.apple.compilers.gcc.4_2
:info:build 	CompileC "build/GitX.build/Release/cli tool.build/Objects-normal/x86_64/PBGitBinary.o" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_GitX/work/GitX-0.7.1/PBGitBinary.m normal x86_64 objective-c com.apple.compilers.gcc.4_2
:info:build 	CompileC "build/GitX.build/Release/cli tool.build/Objects-normal/x86_64/gitx.o" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_GitX/work/GitX-0.7.1/gitx.m normal x86_64 objective-c com.apple.compilers.gcc.4_2
:info:build GitX:
:info:build 	CpResource build/Release/GitX.app/Contents/Resources/gitx build/Release/gitx
:info:build (4 failures)
:info:build 
:info:build shell command "cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_GitX/work/GitX-0.7.1" && /usr/bin/xcodebuild  -target "GitX" -configuration Release build OBJROOT=build/ SYMROOT=build/ MACOSX_DEPLOYMENT_TARGET=10.6 ARCHS=x86_64 SDKROOT="" " returned error 1
:error:build Target org.macports.build returned: shell command failed (see log for details)
:debug:build Backtrace: shell command failed (see log for details)
    while executing
"$procedure $targetname"
:info:build Warning: the following items did not execute (for GitX): org.macports.activate org.macports.build org.macports.destroot org.macports.install

No real idea what’s wrong. I have MacPorts 1.9.2 on Mac OS X 10.6.5 with Xcode 3.2.5.

[larryv@…]

Build log from attempted GitX install

[larryv@…]

I should probably mention that I reinstalled vanilla git-core just in case, but GitX failed there too.

[jmr@…]

Looks like Xcode's PCH cache is corrupt. Try the "Empty Caches…" menu item in Xcode.app.

[larryv@…]

Replying to jmr@…:

Looks like Xcode's PCH cache is corrupt. Try the "Empty Caches…" menu item in Xcode.app.

Tried that twice, the build still fails. Same error.

[larryv@…]

Replying to larryv@…:

Tried that twice, the build still fails. Same error.

Never mind, tried it three or four more times for fun and now port install GitX works. Thanks.

[larryv@…]

Replying to larryv@…:

Never mind, tried it three or four more times for fun and now port install GitX works. Thanks.

Never mind. I'd created a Portfile for GitX in a local ports repository, and it built correctly using that. But when I removed it so that MacPorts would use the master repository again, it failed.

Instead, I just deleted /var/folders/zz/zzzivhrRnAmviuee+++++++++++/-Caches-/, which was referenced in one of the error messages in the log file. It works now.

[raimue@…]

Port abandoned after #30605, assigning to new maintainer.

[cal@…]

Closing, since the issue has apparently been solved.

[deesto@…]

I just had the same thing happen, during a 'port upgrade outdated', which first updated git-core and then tried to update GitX, which failed to build with a series of errors. Just a simple retry of upgrading the package again worked fine, which seems strange to me.