Add-ons can't be installed with Node.js v6.0.0-rc.2

[fivdi]

• Version: v6.0.0-rc.2
• Platform: Linux raspberrypi 4.1.18-v7+ benchmark: add a few querystring benchmarks #846 SMP Thu Feb 25 14:22:53 GMT 2016 armv7l GNU/Linux

Attempting to install add-ons with Node.js v6.0.0-rc.2 results in the error shown below. node-v6.0.0-rc.2-headers.tar.gz can't be found at https://nodejs.org/download/release/v6.0.0-rc.2/node-v6.0.0-rc.2-headers.tar.gz because it's not there. It's located at https://nodejs.org/download/rc/v6.0.0-rc.2/node-v6.0.0-rc.2-headers.tar.gz

pi@raspberrypi:~/junk $ npm install epoll

> epoll@0.1.17 install /home/pi/junk/node_modules/epoll
> node-gyp rebuild

gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack Error: 404 response downloading https://nodejs.org/download/release/v6.0.0-rc.2/node-v6.0.0-rc.2-headers.tar.gz
gyp ERR! stack     at Request.<anonymous> (/home/pi/opt/node-v6.0.0-rc.2-linux-armv7l/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:210:14)
gyp ERR! stack     at emitOne (events.js:95:20)
gyp ERR! stack     at Request.emit (events.js:182:7)
gyp ERR! stack     at Request.onRequestResponse (/home/pi/opt/node-v6.0.0-rc.2-linux-armv7l/lib/node_modules/npm/node_modules/request/request.js:952:10)
gyp ERR! stack     at emitOne (events.js:90:13)
gyp ERR! stack     at ClientRequest.emit (events.js:182:7)
gyp ERR! stack     at HTTPParser.parserOnIncomingClient (_http_client.js:469:21)
gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (_http_common.js:103:23)
gyp ERR! stack     at TLSSocket.socketOnData (_http_client.js:359:20)
gyp ERR! stack     at emitOne (events.js:90:13)
gyp ERR! System Linux 4.1.18-v7+
gyp ERR! command "/home/pi/opt/node-v6.0.0-rc.2-linux-armv7l/bin/node" "/home/pi/opt/node-v6.0.0-rc.2-linux-armv7l/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pi/junk/node_modules/epoll
gyp ERR! node -v v6.0.0-rc.2
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok 
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/junk/package.json'
npm WARN junk No description
npm WARN junk No repository field.
npm WARN junk No README data
npm WARN junk No license field.
npm WARN You are using a pre-release version of node and things may not work as expected
npm ERR! Linux 4.1.18-v7+
npm ERR! argv "/home/pi/opt/node-v6.0.0-rc.2-linux-armv7l/bin/node" "/home/pi/opt/node-v6.0.0-rc.2-linux-armv7l/bin/npm" "install" "epoll"
npm ERR! node v6.0.0-rc.2
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE

npm ERR! epoll@0.1.17 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the epoll@0.1.17 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the epoll package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs epoll
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls epoll
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/junk/npm-debug.log
pi@raspberrypi:~/junk $ 

[Qard]

Did you try to install by dumping into the nvm versions folder? This is a common issue with dumping prerelease versions into nvm. It's due to the NVM_NODEJS_ORG_MIRROR env variable. Try setting it to an empty string and try again.

[fivdi]

I'm not using nvm in this case. I was able to workaround the issue by manually downloading and decompressing node-v6.0.0-rc.2-headers.tar.gz and then calling npm install with the --nodedir option.

pi@raspberrypi:~ $ wget https://nodejs.org/download/rc/v6.0.0-rc.2/node-v6.0.0-rc.2-headers.tar.gz
pi@raspberrypi:~ $ tar -zxf node-v6.0.0-rc.2-headers.tar.gz 
pi@raspberrypi:~ $ npm install epoll --nodedir=/home/pi/node-v6.0.0-rc.2
> epoll@0.1.17 install /home/pi/node_modules/epoll
> node-gyp rebuild

make: Entering directory '/home/pi/node_modules/epoll/build'
  CXX(target) Release/obj.target/epoll/src/epoll.o
  SOLINK_MODULE(target) Release/obj.target/epoll.node
  COPY Release/epoll.node
make: Leaving directory '/home/pi/node_modules/epoll/build'
/home/pi
└─┬ epoll@0.1.17 
  ├── bindings@1.2.1 
  └── nan@2.2.1 

npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.
npm WARN You are using a pre-release version of node and things may not work as expected
pi@raspberrypi:~ $ 

[jasnell]

this is due to a bad config setting when the build was generated, I'm running a new build for rc.2 now that should fix the link when it's done

[jasnell]

oh wait... perhaps not... looking the details of the error. When the new build is complete, grab it and see if it resolves the issue.

[MylesBorins]

I just installed the new build of rc.2 and everything is working as expected now. If you are an nvm user you will have to run

unset NVM_NODEJS_ORG_MIRROR

in order to stop nvm from trumping the gyp path. @ljharb where are we on fixing that in nvm

Closing as things appear to be working

[ljharb]

Fixing what in nvm? As I understand it, it's an issue with node-gyp for relying on an internal nvm env var in the first place :-)

[Qard]

See: nodejs/node-gyp#787

[fivdi]

Yes, the link is fixed with the latest rc.2. What comes as a very pleasant surprise is that the add-on compiles and functions as expected without a single modification. This isn't something that I expected given the major version bump.

[jasnell]

Awesome. Yeah we were pleasantly surprised also to find out there were no
breaking API or ABI changes in this major.
On Apr 15, 2016 10:20 PM, "Brian Cooke" notifications@github.com wrote:

Yes, the link is fixed with the latest rc.2. What comes as a very pleasant
surprise is that the add-on compiles and functions as expected without a
single modification. This isn't something that I expected given the major
version bump.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#6237 (comment)