gcc does not support "-Wno-error=shorten-64-to-32"

[quark-zju]

ruby-build script contains following workaround for clang:

# Work around warnings building Ruby 2.0 on Clang 2.x
if type clang &>/dev/null; then
  if "${CC:-clang}" -x c /dev/null -E -Wno-error=shorten-64-to-32 &>/dev/null; then
    RUBY_CFLAGS="$RUBY_CFLAGS -Wno-error=shorten-64-to-32"
  fi
fi

If both gcc and clang installed and cc is gcc, the above workaround will be triggered wrongly and result in failing to compile anything:

configure:3741: checking whether the C compiler works
configure:3763: gcc   -Wno-error=shorten-64-to-32 -I'/home/quark/.rbenv/versions/2.0.0-p0/include'  -L'/home/quark/.rbenv/versions/2.0.0-p0/lib'  conftest.c  >&5
cc1: error: -Werror=shorten-64-to-32: no option -Wshorten-64-to-32
configure:3767: $? = 1
configure:3805: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define CANONICALIZATION_FOR_MATHN 1
| #define RUBY_BASE_NAME "ruby" !<verconf>!
| #define RUBY_VERSION_NAME RUBY_BASE_NAME"-"RUBY_LIB_VERSION !<verconf>!
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:3810: error: in `/tmp/ruby-build.20130310154119.10022/ruby-2.0.0-p0':
configure:3812: error: C compiler cannot create executables
See `config.log' for more details

How about changing ${CC:-clang} to ${CC:-cc} in the workaround script?

[lpar]

You don't even need to have clang installed to get the problem. I hit it on Debian Stable with only GCC installed, so somehow the "type clang" stuff is being triggered even when the compiler is GCC. Nasty.

[Ivoz]

In short, this is a clang-specific flag; it should only be added if clang is the compiler being used, not universally. This check should be done after we know which compiler is being used.

[alexspeller]

I was just hit by this and spent about 6 hours uninstalling and reinstalling my toolchain because I thought that was the problem. I am an idiot :(

[quark-zju]

This is duplicated with #319.

[jeremy]

Fixed by #339

[stantona]

I am still getting this issue. When I bundle install nokogiri fails to install. My mkmf.log file looks like:

https://photos-1.dropbox.com/t/0/AAC1TjDZ0BD6O3-NxkXZi3KbFo-c4o4Fgg6-Z9gAssWkcA/12/12846094/png/1024x768/3/1401408000/0/2/Screenshot%202014-05-29%2015.18.21.png/P6xlrS6O7FWpaZFZ6w7onpd2tRS5pyWoG4yO7D0hZV0

[mislav]

@stantona: Compiling Nokogiri is different than compiling Ruby. This project only deals with producing working Ruby installations. For compiling Nokogiri please see its troubleshooting docs to see if there are extra steps to install the gem on your system.

[markjreed]

Still seeing this issue trying to build 1.9.3 on Yosemite. The check in the ruby-build script assumes that the compiler used will be either cc or $CC, but if $CC is not set, the ruby 1.9.3 configure script will explicitly look for gcc and use that instead, causing a mismatch. Had to explicitly set CC=gcc purely for ruby-build's benefit, even though the ruby distro builds fine on its own without it.

[lpar]

1.9.3 is EOL in March, just FYI. If you're still building it for some reason, you might want to stop.