Command Line Tools for Xcode - some failed packages on clean 10.7 install

[sud0n1m]

I started this morning with a clean install of OS X 10.7.3. I installed Command Line Tools for Xcode after reading about it here: http://kennethreitz.com/xcode-gcc-and-homebrew.html

A few packages I'm trying to install are:

mysql: Success!
redis: Fail - output here: https://gist.github.com/1860410 (Doesn't build with Clang)
mongo: Success
macvim: Fail - output here https://gist.github.com/1860416 (Make sure xcode-select is pointing at the proper path)
zsh: Success

It seems like Macvim may need Xcode, but there doesn't seem to be an obvious reason for redis to be failing. I might try to install full Xcode, but wanted to report the issue.

[jacknagel]

Redis can be compiled with --use-llvm. There is an fix in upstream hiredis for the clang issue, but it hasn't been ported to redis yet.

I'm not surprise macvim fails, but that should really be taken to MacVim itself.

[jacknagel]

Also, please post build output in a gist rather than inline, it makes the thread impossible to navigate.

[Sharpie]

Perhaps we should apply the following as a patch to Redis until a new release comes out:

https://github.com/antirez/hiredis/compare/5def8643...2da784ce.patch

[Sharpie]

The vim error looks like some bad Xcode paths:

Error: Can't run /usr/bin/usr/bin/xcodebuild (no such file).

Perhaps running xcode-select can clear this up?

[jacknagel]

We could also force ENV.llvm until it's fixed, if we don't want to apply that big of a patch.

[Sharpie]

Doesn't look too bad---the first patch adds some unit tests for the problem and the next to patches fix the way vargs are handled.

[jacknagel]

Slightly off topic, but we should consider adding -Qunused-arguments as a standard flag for clang to silence all these "clang: warning: argument unused during compilation" warnings.

[sud0n1m]

Sorry for posting output inline. Refactored it to use gists.

brew install redis --use-llvm worked like a charm

I installed Xcode... I had originally followed instructions in #10245 to run sudo xcode-select -switch /usr/bin and that caused the /usr/bin/usr/bin/xcodebuild issue. After installing Xcode, I ran sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer to fix that and Macvim installed fine.

[Sharpie]

I had originally followed instructions in #10245 to run sudo xcode-select -switch /usr/bin and that caused the /usr/bin/usr/bin/xcodebuild issue.

Ahh. I think the proper incantation for users who only install the command line tools is:

xcode-select -switch /

[2bits]

sudo xcode-select -switch /
brew --env

hangs indefinitely for me because xcodebuild -version hangs. Nobody who's done a clean install can tell me if it works for them.

[jacknagel]

Closing since redis is fixed and there are a few other XCode 4.3/CLT threads with similar reports.

[vidgizmo]

My problem may be different, but doing the following resolved the issue of building macvim for me:

sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer/

My Xcode came from the App Store, and this is where the install goes now.

[2bits]

I think the preferred path is: /Applications/Xcode.app
I'm not sure about the trailing slash you used. That is not generally ok.

[vidgizmo]

As I understand it this is a replacement for what used to be /Developer.

In any case, macvim and all other packages tried so far seem to be working now.

[2bits]

Right on. We've heard from a lot of people that both those paths work. I don't have the full XCode-4.3, though, to look it up. Can you tell me what it says in man xcodebuild about the path (or maybe in xcode-select)? Thanks.

[jearles]

From my Xcode 4.3 install: man xcode-select

-switch xcode_path
   Sets the path to the current Xcode, e.g. "/Xcode4.2". This command must be run
   with superuser permissions, and will affect all users on the system. To set the path
   without superuser permissions or only for the current shell session, use the
   DEVELOPER_DIR environment variable instead.

    As a convenience, for Xcode 4.3 and later, you can supply just the path to the Xcode
    application, e.g. "/Applications/Xcode.app", and xcode-select will determine the proper
    path to the Developer directory it contains.