From: "mpapis (Michal Papis)" <mpapis@...>
Date: 2012-10-18T23:48:24+09:00
Subject: [ruby-core:48065] [ruby-trunk - Bug #7120] [[Ruby 1.9:]] ${cflags} missing from CFLAGS


Issue #7120 has been updated by mpapis (Michal Papis).


Will this fix be merged back to 1.9.3 or should I rely on my patch when using CFLAGS / LDFLAGS?
----------------------------------------
Bug #7120: [[Ruby 1.9:]] ${cflags} missing from CFLAGS
https://bugs.ruby-lang.org/issues/7120#change-31014

Author: mpapis (Michal Papis)
Status: Closed
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]


=begin
Because ruby does not allow multiple `--with-opt-dir=` - so RVM uses `CFLAGS=`/`LDFLAGS=` to not block `--with-opt-dir=` from users.

This lead to an issue where ruby detected flags are not set if `CFLAGS` is provided earlier.

I did prepare a patch to persist the detected flags in `CFLAGS`: https://gist.github.com/3854178.

There is no way for user to detect the flags by himself, user would have to reproduce the whole ruby detection process to make it working.

The patch puts `${cflags}` before the given `CFLAGS`, so users can still overwrite the auto-detected values as the last flag is relevant.

There is an initial report if more context is needed: https://github.com/wayneeseguin/rvm/issues/1203
=end



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