search

vicoapp / vico

Mac Programmers Text Editor
http://www.vicoapp.com/
657 stars 89 forks source link

Build error on OS X 10.7 #3

Closed dmcdougall closed 12 years ago

dmcdougall commented 12 years ago

I'm getting the following build error:

The following build commands failed:
    CompileC /Users/damon/git/vico/build/DEBUG/sparkle/Sparkle.build/Release/Sparkle.build/Objects-normal/i386/SUAppcast.o SUAppcast.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
make: *** [/Users/damon/git/vico/build/DEBUG/sparkle/Sparkle.stamp] Error 65

Output of xcodebuild -version says I'm using version 4.2.1.

teoljungberg commented 12 years ago

Did you run make run or just make ?

dmcdougall commented 12 years ago

On Mon, Jul 09, 2012 at 11:36:24AM +0000, Teo Ljungberg wrote:

Did you run make run or just make ?

I ran make run.

Damon McDougall http://damon-is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United Kingdom

martinh commented 12 years ago

Is there nothing more than "Error 65" in the output?

I'm using Xcode 4.3.1, according to xcodebuild -version.

dmcdougall commented 12 years ago

On Mon, Jul 09, 2012 at 06:39:02PM +0000, martinh wrote:

Is there nothing more than "Error 65" in the output?

I'm using Xcode 4.3.1, according to xcodebuild -version.

I am just as baffled as you. It's in the running for the most useless error message ever.

It's interesting that you have 4.3.1. I'm using Xcode version 4.3.3, yet xcodebuild -version returns 4.2.1. Blah.

I am in the process of downloading some updates, which I didn't think was possible since I'm using 4.3.3 and AFAIK that's the latest version. I finally decided to man up and opened Xcode and went to Preferences -> Downloads. There's an entry called 'Command Line Tools' that I'm updating. I will report back when this ordeal is over.

For the record, when you open Xcode and go to Xcode -> About Xcode, what version does it say you're using?

Damon McDougall http://damon-is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United Kingdom

dmcdougall commented 12 years ago

No dice. I successfully completed the update and xcodebuild -version still returns 4.2.1.

dmcdougall commented 12 years ago

Good lord. After a ton of faffing around I finally got it.

For everyone else that might be having problems, when I ran xcode-select -print-path it returned /Developer. It turns out that the Mac App Store downloaded the new version of Xcode into /Applications. So I ran sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer. After doing that, xcodebuild -version returned 4.3.3, as it should have done all along. With my new found xcodebuild executable, I tried make run again and everything works.

It might be worth putting this in the readme so nobody else has to go through this nonsense. Sorry for the hassle, and thank you for your help! I really appreciate it.

eobu commented 12 years ago

I was stuck on this. Thank you!

Shadowfiend commented 12 years ago

If you're willing to sacrifice XCode 3, I believe you can use xcrun clang instead of just clang as CC and xcrun clang++ instead of clang++ as CXX. This will properly use the tools for the version currently selected by xcode-select.

I can make that change and pass it on as a pull request if you'd like.

(Note: this lets you avoid separately installing the XCode tools.)

eobu commented 12 years ago

Thanks, but I use the XCode tools for other things so I updated them today, adjusted the path like dmcdougall and now vico builds for me.

Shadowfiend commented 12 years ago

I was more saying as a general inquiry to @martinh if he'd prefer to have the defaults work for XCode as installed.

martinh commented 12 years ago

Yes, please.

10 jul 2012 kl. 05:12 skrev Antonio Salazar Cardozo reply@reply.github.com:

If you're willing to sacrifice XCode 3, I believe you can use xcrun clang instead of just clang as CC and xcrun clang++ instead of clang++ as CXX. This will properly use the tools for the version currently selected by xcode-select.

I can make that change and pass it on as a pull request if you'd like.

Reply to this email directly or view it on GitHub: https://github.com/vicoapp/vico/issues/3#issuecomment-6865874

Shadowfiend commented 12 years ago

Cool, pull request is #8.

dmcdougall commented 12 years ago

If there's no further feedback, is it safe to close this issue?

martinh commented 12 years ago

Yes, this is now merged. 

.martin
dmcdougall commented 12 years ago

Closed. Thanks for the help everyone!

nybblr commented 12 years ago

Hey guys,

Just found the vico project -- really impressed and looking forward to the future of this app =)

Hopefully this doesn't merit reopening the issue and is just a compatibility issue. I ran make run from a new git clone, and it fails with the exact same issue mentioned here. I also have Xcode 4.2.1, but now Xcode 4.4 is out with a LOT of issues (by the app store reviews) I really don't want to upgrade yet -- is it possible to compile Vico with 4.2.1? I haven't seen a download link for Xcode 4.3.3.

Just for reference, here's what I get under "BUILD FAILED":

The following build commands failed:
    CompileC /Users/Jonathan/Development/UNIX/vico/build/DEBUG/sparkle/Sparkle.build/Release/Sparkle.build/Objects-normal/i386/SUAppcast.o SUAppcast.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
make: *** [/Users/Jonathan/Development/UNIX/vico/build/DEBUG/sparkle/Sparkle.stamp] Error 65

Thanks guys! ~ Jonathan Martin