From: Aaron Patterson Date: 2011-11-19T03:02:43+09:00 Subject: [ruby-core:41138] Re: [ruby-trunk - Bug #5541][Open] Better configure error message when llvm-gcc is the default compiler --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 19, 2011 at 02:07:32AM +0900, Motohiro KOSAKI wrote: >=20 > Issue #5541 has been updated by Motohiro KOSAKI. >=20 > Status changed from Closed to Open > Assignee changed from Ryan Davis to Eric Hodel >=20 > > Ryan committed r33780. >=20 > No. this is different patch. Eric patch is far better. Maybe the best mes= sage is, >=20 > llvm-gcc is not further supported by ruby. Use gcc or clang (eg. CC= =3Dclang) Why does configure exit when clang is available? Could we have configure test for clang first, then test for gcc? It's annoying that the configure script chooses llvm-gcc when clang is available on my system. --=20 Aaron Patterson http://tenderlovemaking.com/ --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) iQEcBAEBAgAGBQJOxp2+AAoJEJUxcLy0/6/GSuMH+wUIoieZl3jNQbs6PJ5YUeC6 0zH8mZ53pyMumgGVCBbg3YHIomgrk8qdV+bs9nkB9lbKmdfBXf8ESo5ODzm9wsB+ hh3HWYvY8FAWkyVvkIUEfhbMraCPMbwC7S19Orijrud99plV0BDDeRS0qe6Y/cKj Z7Xw/HR5ZyTDJyywV4gYE+/jM4k2FE4PNQpM9bkqu6vwxydYckLibUPumH5W38Zw yaTeRQ/+fxRz+Bq4mPciPJ5yB+B2cvT8ITbibmQ82alBjhdNzbPbmvqD0ZID8qve TinGScPlv32mWKkC7qlL1evJ/kGNM55zlcoLLDc9MD+W4QtwtDrmwvMd2yzFk0A= =Gm3H -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j--