Description of problem: Unable to build and install libraries through npm Version-Release number of selected component (if applicable): nodejs: 0.10.36 nodejs-devel: 0.10.36 libuv: 1.4.0 libuv-devel: 1.4.0 How reproducible: Always Steps to Reproduce: 1. dnf install nodejs nodejs-devel libuv libuv-devel npm 2. npm install ijavascript Actual results: npm WARN package.json foundation-cli.4 No repository field. npm http GET https://registry.npmjs.org/ijavascript npm http 304 https://registry.npmjs.org/ijavascript npm http GET https://registry.npmjs.org/zmq npm http GET https://registry.npmjs.org/node-uuid npm http 304 https://registry.npmjs.org/node-uuid npm http 304 https://registry.npmjs.org/zmq npm http GET https://registry.npmjs.org/bindings npm http GET https://registry.npmjs.org/nan npm http 304 https://registry.npmjs.org/bindings npm http 304 https://registry.npmjs.org/nan > zmq.0 install /home/jzachary/node_modules/ijavascript/node_modules/zmq > node-gyp rebuild make: Entering directory '/home/jzachary/node_modules/ijavascript/node_modules/zmq/build' CXX(target) Release/obj.target/zmq/binding.o In file included from ../binding.cc:25:0: /usr/include/node/node.h:150:46: error: ‘uv_statbuf_t’ does not name a type v8::Local<v8::Object> BuildStatsObject(const uv_statbuf_t* s); ^ /usr/include/node/node.h:252:27: error: variable or field ‘SetErrno’ declared void NODE_EXTERN void SetErrno(uv_err_t err); ^ /usr/include/node/node.h:252:27: error: ‘uv_err_t’ was not declared in this scope zmq.target.mk:88: recipe for target 'Release/obj.target/zmq/binding.o' failed make: *** [Release/obj.target/zmq/binding.o] Error 1 make: Leaving directory '/home/jzachary/node_modules/ijavascript/node_modules/zmq/build' gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:267:23) gyp ERR! stack at ChildProcess.emit (events.js:98:17) gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:820:12) gyp ERR! System Linux 4.0.0-1.fc22.x86_64 gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /home/jzachary/node_modules/ijavascript/node_modules/zmq gyp ERR! node -v v0.10.36 gyp ERR! node-gyp -v v0.10.6 gyp ERR! not ok npm ERR! weird error 1 npm ERR! not ok code 0 Expected results: \ > zmq.0 install /home/jzachary/node_modules/ijavascript/node_modules/zmq > node-gyp rebuild make: Entering directory '/home/jzachary/node_modules/ijavascript/node_modules/zmq/build' CXX(target) Release/obj.target/zmq/binding.o SOLINK_MODULE(target) Release/obj.target/zmq.node SOLINK_MODULE(target) Release/obj.target/zmq.node: Finished COPY Release/zmq.node make: Leaving directory '/home/jzachary/node_modules/ijavascript/node_modules/zmq/build' ijavascript.6 node_modules/ijavascript ├── node-uuid.3 └── zmq.0 (bindings.1, nan.3) Additional info: When use the nodejs 0.12.2 binaries from http://node.js the build and install is successful.
node-gyp-0.10.6-4.fc22,nodejs-0.10.36-4.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/node-gyp-0.10.6-4.fc22,nodejs-0.10.36-4.fc22
Package node-gyp-0.10.6-4.fc22, nodejs-0.10.36-4.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing node-gyp-0.10.6-4.fc22 nodejs-0.10.36-4.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7309/node-gyp-0.10.6-4.fc22,nodejs-0.10.36-4.fc22 then log in and leave karma (feedback).
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.