On Mon, Jun 24, 2013 at 10:40 AM, Thomas Watson <t...@tws.name> wrote: > I just ran a fresh `npm install --production` on a node.js project I've > installed on a new EC2 Ubuntu 10.04 LTS server and to my amazement it tried > to install node v0.8.25 after it was finished downloading and installing all > the required node modules. I've never seen this behavior before. This is how > the output looked: > > gyp http GET http://nodejs.org/dist/v0.8.25/node-v0.8.25.tar.gz > gyp http 200 http://nodejs.org/dist/v0.8.25/node-v0.8.25.tar.gz > gyp ERR! build error > gyp ERR! stack Error: not found: make > gyp ERR! stack at F > (/home/ubuntu/node-v0.8.25-linux-x64/lib/node_modules/npm/node_modules/which/which.js:43:28) > gyp ERR! stack at E > (/home/ubuntu/node-v0.8.25-linux-x64/lib/node_modules/npm/node_modules/which/which.js:46:29) > gyp ERR! stack at > /home/ubuntu/node-v0.8.25-linux-x64/lib/node_modules/npm/node_modules/which/which.js:57:16 > gyp ERR! stack at Object.oncomplete (fs.js:297:15) > gyp ERR! System Linux 3.2.0-40-virtual > gyp ERR! command "node" > "/home/ubuntu/node-v0.8.25-linux-x64/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" > "rebuild" > gyp ERR! cwd > /home/ubuntu/connect/node_modules/socket.io/node_modules/redis/node_modules/hiredis > gyp ERR! node -v v0.8.25 > gyp ERR! node-gyp -v v0.10.0 > gyp ERR! not ok > > I tried to run `npm install --production` again, but this time it didn't try > to install node. It only tried it the first time. > > I've specified the supported node version in package.json using: > "engines": { "node": "=0.8" } > > And before I ran the `npm install --production` command I installed node and > npm using the following set of commands: > wget http://nodejs.org/dist/v0.8.25/node-v0.8.25-linux-x64.tar.gz > tar xzf node-v0.8.25-linux-x64.tar.gz > sudo ln -s ~/node-v0.8.25-linux-x64/bin/node /usr/local/bin/node > sudo ln -s ~/node-v0.8.25-linux-x64/bin/npm /usr/local/bin/npm > > What was it that made it try and install node v0.8.25, when it's clearly > available in the path? And why does NPM even concern it self with this? > > /watson
It doesn't build node, it downloads the tarball so native modules can build against it. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
