-
Notifications
You must be signed in to change notification settings - Fork 785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to prevent MRI from using gcc-4.2 on Yosemite #651
Comments
On the other hand, we might need to require using ❓ 😕 ❓ |
👍 apple-gcc4.2 is compiled by darwin11 arch. it's not compatible Yosemite. Probably it works under darwin13(marvericks) arch. After Yosemite release, We need to use |
Hi everyone, I'm sorry to ruin this but apparently despite I followed all the advises mentioned in the various thread I'm still not able to compile the latest Ruby on Yosemite. I'm currently trying to install 2.1.4 but the following is the log I get: https://gist.github.com/88b061616c44948a00b1 I tried exporting CC with both gcc or clang and I also tried the --without-gcc option and none of them helped. Any additional idea? |
@marcodebortoli Please uninstall apple-gcc42 |
@hsbt thanks that was spot on. So are you guys suggesting, in general, to don't use apple-gcc42 anymore under Yosemite whatsoever? |
On Oct 28, 2014, at 12:54 AM, Marco De Bortoli [email protected] wrote:
Did you literally try setting CC=clang? Can you try again? Because this is enough to tell Ruby build to not look for gcc-4.2 on np the system and is a workaround I'm baking into ruby-build since yesterday.= |
Yes @mislav, I tried setting CC to clang, /urs/bin/gcc, the flag, I also updated the command line tools as suggested in other thread. I'm not sure if the fact I'm using fish shell has anything to do with the failure but definitely something to investigate further. For the time being I uninstalled apple-gcc42 as @hsbt suggested and it compiled. If you need any assistance and you want a guinea pig feel free to ping me :-) |
@marcodebortoli, how did you set CC to clang in fish? Was it |
@marktran nope, |
We removed priority configuration for apple-gcc42 at r48174 |
@marcodebortoli That doesn't seem like you've exported the CC variable to subprocesses. That only sounds like you've set the value for the current shell. |
@mislav you are correct, I forgot to add the |
@marcodebortoli |
+1 |
Newer MRI installs are broken on Yosemite for people who have Homebrew
apple-gcc42
installed. Previously MRIs would findgcc-4.2
in PATH and use it over/usr/bin/gcc
/clang and it would be fine either way, but that doesn't work in Yosemite for some reason.The workaround is easy: set
CC=/usr/bin/gcc
orCC=clang
for the build and Ruby will use clang instead of detectinggcc-4.2
in PATH.We can't expect each person to figure this out by themselves. I propose that on Yosemite we default to CC=clang for MRI >= 1.9.3-p0 if an explicit
CC
wasn't set.Original issue: rbenv/rbenv#610
/cc @hsbt @jeremy
The text was updated successfully, but these errors were encountered: