heroku/heroku-buildpack-nodejs — Issue #7: always end up with a corrupted 64 kb node file
Author: mbuchetics
Created: 2012-01-13 08:25:01+00:00
State: open

Trying to make a custom buildpack but running into some problems. I followed the steps described in this blog: http://blog.superpat.com/2011/11/15/running-your-own-node-js-version-on-heroku/ in addition to the readme.
When I run the package_node script, everything seems to be fine (= no errors) but the resulting file in the S3 bucket is only 64 KB and corrupted.
I tried updating the vulcan build server but I am still running into the same issues.

From time to time, the script also stops with the following error after the build step:
>> Building with: ./configure --prefix /app/vendor/node-v0.6.7 && make install
error: null/Users/matthias/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/net/protocol.rb:135:in `read_nonblock': end of file reached (EOFError)

Any ideas what could be the problem?