-
Notifications
You must be signed in to change notification settings - Fork 778
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
Don't force CC=cc
(if CC is not defined) for all installing phase
#311
Comments
@sstephenson oh, Sorry I don't know But, I still think we should check How about that change? |
Ruby 2.0.0 can choice suitable compiler from gcc-4.2, clang, gcc, and cc in configure.in by itself. Ruby 1.8.7-p371 supports clang (r36253). |
OK - the issue we had with Ruby's auto-detect is that Sounds like we can set CFLAGS to fix that issue, instead. |
What? I don't know an environment which It should be users' problem. |
I may be remembering wrong. Confusing 😁 |
gcc-4.2 is always GNU GCC. cc/gcc can be llvm-gcc. |
Fixed - thank you. |
(Continuing from a0570c9's commit comment)
What's the commit
a0570c9
clang
by specifyingCC=cc
ifCC
isn't set, because ruby-2.0.0-p0 build fails on llvm-gcccc
is symlinked toclang
, butgcc
symlinked tollvm-gcc
andllvm-gcc
make failures.gcc
for default, sollvm-gcc
will be used. and currently build will be failed withllvm-gcc
.Problems
So, I recommend to...
CC=clang
instead ofCC=cc
gcc
isllvm-gcc
CC=clang
into2.0.0-p0
file, because 1.8 doesn't support clang and it makes SEGV on 1.8.The text was updated successfully, but these errors were encountered: