Comments on: OSX, RubyGems and cross-thread violations in rb_gc

By: Pete Campbell

Pete Campbell — Thu, 28 Jul 2011 19:02:04 +0000

Good explanation, but you might want to mention that the offending Gem(s) may also be in vendor/gems or vendor/cache (with Bundler). http://petecampbell.wordpress.com/2011/07/28/cross-thread-violations-on-rb_gc-vendored-gems-eek/

By: Simon

Simon — Sun, 26 Sep 2010 20:07:09 +0000

Thanks, the command of Rolf worked for me (just be careful with your CMS, it changes the normal quotes to smart quotes, Terminal doesn’t like those).

By: Eric Lubow

Eric Lubow — Thu, 08 Jul 2010 00:15:51 +0000

This was really helpful. Saved me what would likely have been hours. Thanks.

By: Xavier Shay

Xavier Shay — Wed, 05 Aug 2009 01:22:44 +0000

to pipe it you need xargs:

ls -1 **/**/*.bundle|ruby -pe ‘$_.gsub! /\-.*/, “”‘|uniq | xargs sudo gem install

if you’re in a rush, you can speed it up a bit by passing –no-rdoc and –no-ri options to gem install.

By: Rolf Bjaanes

Rolf Bjaanes — Fri, 31 Jul 2009 23:42:01 +0000

try this instead to find all the gems:

ruby -rubygems -e ‘p Gem.source_index.find_all { |n,s| !s.extensions.empty? }.map { |n,s| [s.name, s.version.to_s] }’

By: shyam

shyam — Mon, 13 Jul 2009 08:00:48 +0000

I get following errors while going through your insrtuction:
gems $ ls -1 **/**/*.bundle|ruby -pe ‘$_.gsub! /\-.*/, “”‘|uniq
-e:1: Invalid char `\342′ in expression
-e:1: Invalid char `\200′ in expression
-e:1: Invalid char `\230′ in expression
-e:1: syntax error, unexpected ‘.’
‘.gsub!
^
Please suggest me

By: Lance

Lance — Tue, 02 Jun 2009 04:01:57 +0000

thanks man, this really helped me out.

Cheers