-
-
Notifications
You must be signed in to change notification settings - Fork 2k
[1.8.0+] Global build config ignored #3404
Comments
I tracked this down to commit ca7b782. Reverting it fixes compilation on 1.8.2. |
Ugh, definitely need to add a test to make sure that global config is found and not found correctly. Thanks for reporting this! |
This is still broken in 1.9.1. |
Thanks for following up! I'll look at this as soon as possible. |
No worries, let me know if you need more info. Downgraded back to 1.7.x for now. |
Finally tracked this down! The underlying problem turned out to be not configuration but thread-safety: in Bundler 1.8 we switched to using threads to install gems instead of forking, and gem build options are set in a global variable. We've synchronized it for now using a Monitor, but hopefully we can figure out a non-global way to handle build options in the future. |
That sounds like a fun one to debug! ;-) |
Released a fix for this in version 1.8.6, and it will also be fixed in 1.9.2, which I'll release as soon as CI is green. Thanks for the bug report! |
Example (bundler 1.7.13/1.8.2 on Mac OS X 10.10.2 w/homebrew):
Gemfile:
On bundler 1.7.13
extconf.rb --with-opt-dir=/usr/local/opt/libarchive
is called during installation of the gem by bundler:On 1.8.0+ (tested up to 1.8.2) the
--with-opt-dir
flag is not passed to extconf.rb and consequently compilation fails:The text was updated successfully, but these errors were encountered: