Forum: Ruby-core [ruby-trunk - Bug #7120][Open] [[Ruby 1.9:]] ${cflags} missing from CFLAGS

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

----------------------------------------
Bug #7120: [[Ruby 1.9:]] ${cflags} missing from CFLAGS
https://bugs.ruby-lang.org/issues/7120

Author: mpapis (Michal Papis)
Status: Open
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

Issue #7120 has been updated by nobu (Nobuyoshi Nakada).

Status changed from Open to Rejected

--with-opt-dir allows multiple paths separated by File::PATH_SEPARATOR.
----------------------------------------
Bug #7120: [[Ruby 1.9:]] ${cflags} missing from CFLAGS
https://bugs.ruby-lang.org/issues/7120#change-30376

Author: mpapis (Michal Papis)
Status: Rejected
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

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


=begin
Then help for configure should be updated, in current state it indicates 
that it's just one path:

    --with-opt-dir=DIR      add optional headers and libraries DIR
=end

----------------------------------------
Bug #7120: [[Ruby 1.9:]] ${cflags} missing from CFLAGS
https://bugs.ruby-lang.org/issues/7120#change-30885

Author: mpapis (Michal Papis)
Status: Rejected
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

Issue #7120 has been updated by nobu (Nobuyoshi Nakada).

Status changed from Rejected to Open


----------------------------------------
Bug #7120: [[Ruby 1.9:]] ${cflags} missing from CFLAGS
https://bugs.ruby-lang.org/issues/7120#change-30927

Author: mpapis (Michal Papis)
Status: Open
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

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

Issue #7120 has been updated by usa (Usaku NAKAMURA).

Status changed from Closed to Assigned
Assignee set to usa (Usaku NAKAMURA)
Target version set to 1.9.3

It'll be backported.
----------------------------------------
Bug #7120: [[Ruby 1.9:]] ${cflags} missing from CFLAGS
https://bugs.ruby-lang.org/issues/7120#change-31027

Author: mpapis (Michal Papis)
Status: Assigned
Priority: Normal
Assignee: usa (Usaku NAKAMURA)
Category:
Target version: 1.9.3
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