Bug #5541
closed
Better configure error message when llvm-gcc is the default compiler
Added by drbrain (Eric Hodel) almost 14 years ago. Updated over 13 years ago.
Description
The error message ./configure gives when llvm-gcc is the default compiler is not very helpful. This patch gives a better message.
Files
| configure.in.llvm-gcc.patch (682 Bytes) configure.in.llvm-gcc.patch | drbrain (Eric Hodel), 11/02/2011 05:32 AM | ||
| noname (500 Bytes) noname | Anonymous, 11/19/2011 03:23 AM |
Updated by kosaki (Motohiro KOSAKI) almost 14 years ago
Actions
#1
[ruby-core:40661]
The error message ./configure gives when llvm-gcc is the default compiler is not very helpful. Â This patch gives a better message.
+1
Updated by daneharrigan (Dane Harrigan) almost 14 years ago
Actions
#2
[ruby-core:40676]
I completely agree. I was hit with "llvm-gcc has ended" this morning.
Updated by kosaki (Motohiro KOSAKI) almost 14 years ago
Actions
#3
[ruby-core:41118]
ping?
Updated by naruse (Yui NARUSE) almost 14 years ago
Actions
#4
[ruby-core:41120]
- Status changed from Open to Closed
- Assignee set to zenspider (Ryan Davis)
Ryan committed r33780.
To Ryan
Please include ticket number in the commit log like [Bug #5541].
If you include it, then Redmine detect it and close the ticket.
Updated by kosaki (Motohiro KOSAKI) almost 14 years ago
Actions
#5
[ruby-core:41137]
- Status changed from Closed to Open
- Assignee changed from zenspider (Ryan Davis) to drbrain (Eric Hodel)
Ryan committed r33780.
No. this is different patch. Eric patch is far better. Maybe the best message is,
llvm-gcc is not further supported by ruby. Use gcc or clang (eg. CC=clang)
Updated by Anonymous almost 14 years ago
Actions
#6
[ruby-core:41138]
On Sat, Nov 19, 2011 at 02:07:32AM +0900, Motohiro KOSAKI wrote:
Issue #5541 has been updated by Motohiro KOSAKI.
Status changed from Closed to Open
Assignee changed from Ryan Davis to Eric HodelRyan committed r33780.
No. this is different patch. Eric patch is far better. Maybe the best message is,
llvm-gcc is not further supported by ruby. Use gcc or clang (eg. CC=clang)
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.
--
Aaron Patterson
http://tenderlovemaking.com/
Updated by kosaki (Motohiro KOSAKI) almost 14 years ago
Actions
#7
[ruby-core:41139]
Ryan committed r33780.
No. this is different patch. Eric patch is far better. Maybe the best message is,
  llvm-gcc is not further supported by ruby.  Use gcc or clang (eg. CC
Updated by drbrain (Eric Hodel) over 13 years ago
Actions
#8
[ruby-core:42847]
Closing this issue due to r34278
Updated by drbrain (Eric Hodel) over 13 years ago
Actions
#9
[ruby-core:42848]
- Status changed from Open to Closed