Closed florianfunke closed 11 years ago
Sorry, I can't reproduce on 8-core intel sandybridge. For me it builds.
Perhaps someone with CPU: quad-core 64-bit arrandale
, too, can try?
Looks like some CPU flags thing. Does it build when you brew install --verbose valgrind --env=std
?
Thanks for getting back. I tried it again as you suggested, but the outcome is the same.
Can anybody reproduce this? I find it strange that the are some AMD defines in the posted excerpt. I don't have the time to check my build log.
I get a similar error and somehow mine is also seems to be going for AMD.
config & output https://gist.github.com/4615445
Does it help if you add --use-llvm
to the build flags?
Yes. Thanks!
It built just fine on my core2 mbp.
Do we add fails_with :clang
for 10.8 here?
No. I can successfully build valgrind on my system with clang:
brew --config
HOMEBREW_VERSION: 0.9.4
ORIGIN: https://github.com/mxcl/homebrew.git
HEAD: 2fd984f7f503673acae9c7b37e030532e5e458dd
HOMEBREW_PREFIX: /homebrew
HOMEBREW_CELLAR: /homebrew/Cellar
CPU: 8-core 64-bit sandybridge
OS X: 10.8.2-x86_64
Xcode: 4.6
LLVM-GCC: build 2336
Clang: 4.2 build 425
X11: 2.7.4 => /opt/X11
The original bug report has 0.9.3
and is on Xcode 4.5. I'd suggest doing brew update
and updating to Xcode 4.6 + newer CLT at least; not much we can do in the meanwhile I think.
When running with --verbose, I get:
Full output: https://gist.github.com/4307949
The Doc just tells me that my "[...] system is raring to brew."
config.log: https://gist.github.com/4307917