Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bundle install on fresh server (no gems) errors on installing xapian-full-alaveteli #611

Closed
crowbot opened this issue Sep 19, 2012 · 5 comments
Milestone

Comments

@crowbot
Copy link
Member

crowbot commented Sep 19, 2012

Installing xapian-full-alaveteli (1.2.9.5) with native extensions
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

    "/usr/bin/ruby1.8" -rubygems /home/nuvasuparati/.bundler/tmp/2038/gems/rake-0.9.2.2/bin/rake RUBYARCHDIR=/home/nuvasuparati/.bundler/tmp/2038/gems/xapian-full-alaveteli-1.2.9.5/lib RUBYLIBDIR=/home/nuvasuparati/.bundler/tmp/2038/gems/xapian-full-alaveteli-1.2.9.5/lib

/usr/bin/ruby1.8: No such file or directory -- /home/nuvasuparati/.bundler/tmp/2038/gems/rake-0.9.2.2/bin/rake (LoadError)

Gem files will remain installed in /home/nuvasuparati/.bundler/tmp/2038/gems/xapian-full-alaveteli-1.2.9.5 for inspection.
Results logged to /home/nuvasuparati/.bundler/tmp/2038/gems/xapian-full-alaveteli-1.2.9.5/./gem_make.out

An error occurred while installing xapian-full-alaveteli (1.2.9.5), and Bundler cannot continue.
Make sure that gem install xapian-full-alaveteli -v '1.2.9.5' succeeds before bundling.

@crowbot
Copy link
Member Author

crowbot commented Sep 19, 2012

This looks like an issue with bundler trying to reference the rake executable from a temporary location when it's just been installed and no longer exists at that location. I believe this is resolved by making rake and explicit dependency (with version specification) in the Gemfile in 249d0bc.

@crowbot crowbot closed this as completed Sep 19, 2012
@crowbot crowbot reopened this Sep 24, 2012
@crowbot
Copy link
Member Author

crowbot commented Sep 24, 2012

Have confirmed that this doesn't in fact resolve the issue on a system where no version of rake is installed. Have opened an issue with bundler to see if they can throw any light on why this is happening, or suggest workarounds rubygems/bundler#2107

@crowbot
Copy link
Member Author

crowbot commented Sep 27, 2012

So https://github.com/indirect suggests in the issue referenced above that the referencing of a Rakefile in the gemspec extensions is unusual - this may be the problem - next step I guess make be to try wrapping the build rake task in an extconf.rb file and referencing that from the gemspec instead.

@crowbot
Copy link
Member Author

crowbot commented Nov 27, 2012

I now believe this is a bundler issue - see upstream pull request rubygems/bundler#2187

@crowbot
Copy link
Member Author

crowbot commented Feb 1, 2013

I believe with 78c55bf this is now fixed. Gems are installed in vendor/bundle even when STAGING is set to 1.

@crowbot crowbot closed this as completed Feb 1, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant