Use -rrbconfig rather than -rmkmf to load rbconfig
Both seem to work, but it's better to ask for the module we actually want rather than rely on it being pulled in indirectly. See #305.
This commit is contained in:
parent
be4065531e
commit
4fed2e6690
1 changed files with 1 additions and 1 deletions
|
|
@ -1508,7 +1508,7 @@ if test -n "$RUBY"; then
|
||||||
# Try Ruby1.9+ first
|
# Try Ruby1.9+ first
|
||||||
RUBYDIR=`($RUBY -rrbconfig -e 'print RbConfig::CONFIG[["rubyhdrdir"]] || $rubyhdrdir') 2>/dev/null`
|
RUBYDIR=`($RUBY -rrbconfig -e 'print RbConfig::CONFIG[["rubyhdrdir"]] || $rubyhdrdir') 2>/dev/null`
|
||||||
if test x"$RUBYDIR" = x"" || test x"$RUBYDIR" = x"nil"; then
|
if test x"$RUBYDIR" = x"" || test x"$RUBYDIR" = x"nil"; then
|
||||||
RUBYDIR=`($RUBY -rmkmf -e 'print RbConfig::CONFIG[["archdir"]] || $archdir') 2>/dev/null`
|
RUBYDIR=`($RUBY -rrbconfig -e 'print RbConfig::CONFIG[["archdir"]] || $archdir') 2>/dev/null`
|
||||||
else
|
else
|
||||||
RUBYARCH=`($RUBY -rrbconfig -e 'print RbConfig::CONFIG[["arch"]] || $arch') 2>/dev/null`
|
RUBYARCH=`($RUBY -rrbconfig -e 'print RbConfig::CONFIG[["arch"]] || $arch') 2>/dev/null`
|
||||||
fi
|
fi
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue