lloyd / node-toobusy

Build Node.JS servers that don't fall over.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Stuck at node-gyp rebuild

didasy opened this issue · comments

OS@Ubuntu 12.10
Node@v0.8.18
toobusy@v0.2.2

I got this while installing from NPM

> toobusy@0.2.2 install /home/dida/nodejs/pics.kerok.in/node_modules/toobusy
> node-gyp rebuild

gyp http GET http://nodejs.org/dist/v0.8.18/node-v0.8.18.tar.gz
gyp http 200 http://nodejs.org/dist/v0.8.18/node-v0.8.18.tar.gz

and it stuck there forever.

reproducible 100% of the time?

On Feb 3, 2013, at 7:47 AM, Andida Syahendar notifications@github.com wrote:

OS@Ubuntu 12.10
Node@v0.8.18
toobusy@v0.2.2

I got this while installing from NPM

toobusy@0.2.2 install /home/dida/nodejs/pics.kerok.in/node_modules/toobusy
node-gyp rebuild

gyp http GET http://nodejs.org/dist/v0.8.18/node-v0.8.18.tar.gz
gyp http 200 http://nodejs.org/dist/v0.8.18/node-v0.8.18.tar.gz
and it stuck there forever.


Reply to this email directly or view it on GitHub.

Yes, it still won't passed that on my machine. But it works flawlessly on my VPS ( also running 12.10 ).

that's a big download. could you be network constrained?

I don't really know, do you have any suggestion on how to test it?

@JesusIslam - I'll suggest just doing the npm install toobusy and just let that run. There's no feedback while that process downloads and extracts the header files. On a "slow" connection with nothing previously cached it can take several minutes. Just see if it finishes "after a while".

@jrgm
@lloyd was right, it was my ISP. It somehow won't play nice with a big download over NPM.

Thank you, you can close this issue :)