Getting undefined constant RbConfig when using --standalone on bundler 1.3

[myronmarston]

Travis recently upgraded their VMs to bundler 1.3. This is breaking our rspec builds because we use bundle install --standalone --binstubs to install our bundle and run things w/o bundler loaded at runtime (there's a history I won't go into here about why that matters for us). I've traced it back to this commit, where @hone added some code to the generated setup.rb file that references RbConfig. Problem is, you apparently have to require rbconfig before on some rubies:

➜  bundler git:(master) ✗ irb
1.8.7 :001 > RbConfig
NameError: uninitialized constant RbConfig
    from (irb):1
1.8.7 :002 > require 'rbconfig'
 => true 
1.8.7 :003 > RbConfig
 => Config 

...so we're suddenly getting lots of undefined constant errors on travis:

https://travis-ci.org/rspec/rspec-expectations/jobs/5400894/#L118

I think maybe you just need to add the require to fix it?

[indirect]

you always have the craziest edge cases :) yeah, sounds like we just need to require it before it gets used.

[indirect]

fixed, I hope

[myronmarston]

Thanks for addressing this issue so quickly!

[myronmarston]

For anyone else running into this, I was able to work around the issue on travis by setting RUBYOPT:

export RUBYOPT='-rrbconfig'