From: Luis Lavena <redmine@...>
Date: 2010-03-24T09:13:23+09:00
Subject: [ruby-core:28915] [Bug #3002] Hardcoded "gcc" in generated Ruby Makefile

Issue #3002 has been updated by Luis Lavena.


darix,

I would disagree on your statement.

A Makefile generated by configure (autoconf) has the options to override CC, LD, RANLIB, AR and CXX by default.

That is true to compile Ruby, and the information is collected in rbconfig for later usage by mkmf

The problem is that the generated Makefile from mkmf uses the hardcoded compiler instead of honor the override nature of the autoconf makefiles, making hard to switch gcc for llvm-gcc as compiler front-end

And yes, llvm-gcc can build and work as replacement of gcc without any change, except the above hardcoded information.

llvm-gcc has been very helpful for a couple of projects to trace pointer and possible segmentation failures during development.

The change in the way rbconfig and mkmf uses LDSHARED's compiler definition will ease that path.

Thank you
--
Luis Lavena

----------------------------------------
http://redmine.ruby-lang.org/issues/show/3002

----------------------------------------
http://redmine.ruby-lang.org