Open joshminnie opened 6 years ago
@joshminnie Did you by chance install Mac OS High Sierra right before this started happening?
For me it's happening with any ruby shell script.
foo.rb
#!/usr/bin/ruby
🌶 $ ./foo.rb
Ignoring bcrypt-3.1.11 because its extensions are not built. Try: gem pristine bcrypt --version 3.1.11
Ignoring bcrypt-3.1.10 because its extensions are not built. Try: gem pristine bcrypt --version 3.1.10
Ignoring bigdecimal-1.3.2 because its extensions are not built. Try: gem pristine bigdecimal --version 1.3.2
Ignoring bigdecimal-1.3.1 because its extensions are not built. Try: gem pristine bigdecimal --version 1.3.1
Ignoring bindex-0.5.0 because its extensions are not built. Try: gem pristine bindex --version 0.5.0
Ignoring byebug-9.1.0 because its extensions are not built. Try: gem pristine byebug --version 9.1.0
Ignoring byebug-9.0.6 because its extensions are not built. Try: gem pristine byebug --version 9.0.6
Ignoring byebug-8.2.1 because its extensions are not built. Try: gem pristine byebug --version 8.2.1
Ignoring curses-1.2.3 because its extensions are not built. Try: gem pristine curses --version 1.2.3
Ignoring debug_inspector-0.0.3 because its extensions are not built. Try: gem pristine debug_inspector --version 0.0.3
Ignoring debug_inspector-0.0.2 because its extensions are not built. Try: gem pristine debug_inspector --version 0.0.2
After uninstalling each gem, and reinstalling as needed I'm down to this:
🌶 $ ./foo.rb
Ignoring byebug-9.1.0 because its extensions are not built. Try: gem pristine byebug --version 9.1.0
@duffyjp I am currently on Sierra, it's been happening for a while and I've been attempting to fix it through various cleanups. I even went so far as to uninstall all my rubies and gemsets. Which is why I'm at a loss for the difference.
I figured out what the problem was. I'm not sure this is the right solution, but my system default ruby was 2.4.0, while the ruby for the project I was in was 2.2.2. Once I switched my system default ruby to 2.2.2, it worked again.
I did not have executable path defined in Atom settings because I thought using the command bundle exec rubocop
would be sufficient.
gem pristine --all
I've been racking my brain trying to figure out why this occurs, but whenever I linter-reek is enabled within Atom, it errors out constantly with a series of "extensions are not built" messages.
Background and things I've tried:
/Users/josh/.rvm/gems/ruby-2.2.2/bin/reek
. Running specifically in the default ruby/gemset, which would call on this pass when I callreek
from the command line works fine.