-
Notifications
You must be signed in to change notification settings - Fork 24
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
Origen support Bundler 2.X? #332
Comments
As has been discussed previously, The installation guide does say to add If you don't have that it may or may not work, just depending on how your default system gems compare to your application requirements. I haven't tried Bundler 2.0, but from looking at the release notes for it I wouldn't expect Origen to have any issues with it, though nor would I expect it to fix this issue you are having. |
@ginty I believe I have converted my environment and our app to exactly what is recommended. My path has PATH=/nfs/tools/lsf/9.1/linux2.6-glibc2.3-x86_64/etc:/nfs/tools/lsf/9.1/linux2.6-glibc2.3-x86_64/bin:./lbin:... So why isn't the binstub working? |
Not easy to answer that, does it work if you invoke the binstub directly?
|
@ginty We removed the old version of bundler and now get this error message: -bash-4.2$ ./lbin/origen i
/nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 'bundler' (~> 1.7) - did find: [bundler-2.0.1] (Gem::LoadError)
Checked in 'GEM_PATH=/home/bcaqueli/.gem/ruby/2.3.0:/nfs/local/.package/ruby-2.3.1/lib/ruby/gems/2.3.0', execute `gem env` for more information
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/specification.rb:1438:in `block in activate_dependencies'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/specification.rb:1427:in `each'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/specification.rb:1427:in `activate_dependencies'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/specification.rb:1409:in `activate'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems.rb:196:in `rescue in try_activate'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems.rb:193:in `try_activate'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:125:in `rescue in require'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in `require'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/origen-0.36.1/lib/origen.rb:15:in `<top (required)>'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/origen-0.36.1/lib/origen/site_config.rb:12:in `require_relative'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/origen-0.36.1/lib/origen/site_config.rb:12:in `<class:SiteConfig>'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/origen-0.36.1/lib/origen/site_config.rb:2:in `<module:Origen>'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/gems/2.3.0/gems/origen-0.36.1/lib/origen/site_config.rb:1:in `<top (required)>'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in `require'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in `rescue in require'
from /nfs/local/.package/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in `require'
from ./lbin/origen:22:in `<main>' But to answer your question using the full path to the lbin bundler didn't work either. |
I think you should forget about Bundler 2.0 for now and re-install a working version of Bundler again at system level, run After you've done that can you post the output from running |
Don't think the |
If it still doesn't work after that, try deleting your existing |
Hi,
We are finally moving to updated hardware and software and are having issues running origen commands. We have to prepend 'bundle exec ' to every origen command for it to work.
I notice we are using an old version of bundle. Is there any way to run bundler 2.X?
thx
The text was updated successfully, but these errors were encountered: