-
Notifications
You must be signed in to change notification settings - Fork 62
Contextify fails to install in Node 4.2.1 on OSX 10.11 (El Capitan). #188
Comments
Confirming error @chevex : So, I don't think it's your Mac, at least; nor XCode, as I probably have a slightly older version of it than you do (Xcode 4.6.2), but I'm getting the same errors. |
I have the same thing on my Ubuntu |
same on OS X El Capitan running Node 4.2.1 |
+1 same here. Referenced it earlier here: Try downgrading to node 0.12.7 , that oughta work. If you use homebrew do the following. Ensure you have homebrew/versions installed:
Unlink your current node if necessary
Install 0.12.7
|
Same issue here. |
Reproducible on CentOS release 6.7 (Final) as well. |
+1 same here, on El Capitan and Node v4.2.1 |
+1 for Downgrading to node 0.12.7 working. Thanks sp00ne |
+1 same issue, downgrading to 0.12 worked |
+1 waiting for this to be closed to upgrade to 4x. |
+1 for 4x. |
+1 |
+1 for bumping up to 4x. (Although downgrading to 0.12.7 may work for some, I'm stuck with 4x :) |
@idoby branch-point/mas@93e6d9c might be useful in getting C++11 working on travis |
@houli Thanks, I got it to pass and learned something about Travis CI! |
Had same issue, rebooting did nothing, I tried to symlink
didn't work. I tried updating xcode, didn't work, Uninstalled xcode and used only cli tools, failed, installed a fresh xcode
I tried with both system and stable node versions using nvm
I always get something like this;
tldrFound current issue, Thanks @sp00ne
:D |
+1 on ArchLinux, Node 4.2.1. Looking forward for fix. |
same on El Capitan +1 |
Also happening with Node 5. 0 on OS X 10.11. |
Still occurring on ArchLinux with Node 5.0 |
+1 node 5.0 El Capitan |
+1 node 5.0 Yosemite and El Capitan |
+1 Faced the same issue with node v5.0.0 on El Capitan. |
Same over here. Any plans on supporting Node 4.0.0+? |
Just FYI to folks who are here because contextify is being pulled in as a dep of JSdom - the latest version of JSdom no longer has a dependency on contextify. Bumping JSdom versions may fix your problem. |
@qrohlf thganks man!:) |
+1 node 5.0 El Capitan |
might be a dup of #171 |
+1 for OS X 10.11 running Node 4.1.2 and Node 5. It installs fine running Node 0.10.36. |
+1 |
Fixed in 0.1.15 |
Still have that on Windows and node 0.12.7
|
|
Does it really need to compile binaries? |
It does. This is a C++ module. |
Ah ok. Never needed python to install npm packages so far, they always had a non native fallback. |
Great, glad it's working for you. |
still getting this error: |
even for 23:17:42 npm ERR! contextify@0.1.15 install: `node-gyp rebuild`
23:17:42 npm ERR! spawn ENOENT
23:17:42 npm ERR!
23:17:42 npm ERR! Failed at the contextify@0.1.15 install script 'node-gyp rebuild'.
23:17:42 npm ERR! Make sure you have the latest version of node.js and npm installed.
23:17:42 npm ERR! If you do, this is most likely a problem with the contextify package,
23:17:42 npm ERR! not with npm itself.
23:17:42 npm ERR! Tell the author that this fails on your system:
23:17:42 npm ERR! node-gyp rebuild
23:17:42 npm ERR! You can get information on how to open an issue for this project with:
23:17:42 npm ERR! npm bugs contextify
23:17:42 npm ERR! Or if that isn't available, you can get their info via:
23:17:42 npm ERR! npm owner ls contextify
23:17:42 npm ERR! There is likely additional logging output above. |
I just put |
I'm running Ubuntu 14.04 run: Well... It did for me! :) |
Still getting this error. Windows 10 |
I'm running Ubuntu 14.04 and sudo apt-get -y install g++ didn't work for me either.. I have node 7.4.0 though... |
Вот вы же заебали, этим надо node 0.12, другому дураку только 6.9.2, вот я как ебучий пролетарий ебучего кода что должен делать по вашему? Какого хуя эти пизда зависит от цен на пиво, а не от инженерных мыслей? Вот какого хуя? |
Not working on the newest version |
Reproduction steps:
npm install contextify
.I've tried everything I could think of to get this working but nothing seems to help. I tried updating Xcode, re-installing node, re-installing NVM, re-installing homebrew, installing node manually, etc. Nothing seems to get this installing in Node 4.x. It does work if I downgrade to node 0.12.x, but our project is already taking advantage of some things in Node 4.x. This is the only module in our dependency tree that is failing in Node 4.
I've also opened an issue in the node-gyp tracker as well: nodejs/node-gyp#774
The text was updated successfully, but these errors were encountered: