Closed getafive closed 13 years ago
Huh -- that's awfully strange, because Jammit's source contains no reference to the "popen4" gem. -- Perhaps it's in a different gem that Jammit depends on?
I can confirm that this happens when moving from 0.6.0 => 0.6.1 in my Rails 3.0.8 app.
$ rake jammit:package /usr/lib/ruby/gems/1.8/gems/POpen4-0.1.4/lib/popen4.rb:81: [BUG] Segmentation fault ruby 1.8.7 (2010-06-23 patchlevel 299) [i686-linux]
(The rake task simply calls Jammit.package!)
Confirm, I get this on my machine at Jammit 0.6.3 moving from 0.5.4.
@jashkenas yui-compressor
, which Jammit lists as a dependency, started depending on POpen4
as of 0.9.6
. Specifically, https://github.com/sstephenson/ruby-yui-compressor/commit/610395b0147ec9a9648b861f8d2e846d4003d1c8 marks the change.
Great -- please open this issue as a ticket on the ruby-yui-compressor gem.
For rails 3.1.3 => gem win32-open3-19
I just installed jammit 0.6.0 in a Rails 3 app on Mac OS 10.6. When trying to run "jammit" in that Rails app, I get the following error:
This is the entirety of my assets.yml:
Googling this error message yields no results. I ended up fixing the problem by upgrading Ruby from 1.8.7 to 1.9.2 (via rvm). Running jammit again created the asset files properly.
Not sure if this is technically a jammit issue, but I figured it submit it here so that it's documented somewhere.