Closed rodincave closed 10 years ago
Hi Nikolay,
One of our devs is testing it on a Windows 8 machine now. I will update you as soon as I receive a status update.
Cheers, Simon
@rodincave You need to upgrade to v0.11.14, v0.11.8 is too old.
@rodincave Please upgrade to v0.11.14 as @bnoordhuis suggested and let us know if that works for you.
I tried with 0.11.14 nigthly build, but got this error :
D:\web\StreamRoot\Server\v2\node_modules\strong-agent>node "
Data\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\no
bin\node-gyp.js" rebuild
gyp WARN install got an error, rolling back install
gyp ERR! configure error
gyp ERR! stack Error: 404 status code downloading tarball
...
So I installed the 0.11.13 version and the npm install worked, thanks
No problem.
For anyone looking at this later, node-gyp doesn't handle nightly releases or pre-releases.
@rodincave you should be able to install a regular release of v0.11.14; it was released a couple of weeks ago: http://blog.nodejs.org/2014/09/24/node-v0-11-14-unstable/
node-gyp doesn't handle nightly releases or pre-releases
It kind of does but it's not very straightforward. You can either pass --nodedir /path/to/node
to node-gyp or run env npm_config_nodedir=/path/to/node npm install whatever
. Both cases require a source checkout, however.
@rmg thanks, I actually tried with the 0.11.14 you linked, but still had the same issue of 404, so i am not sure it was a nigthly build issue
Hi,
I am trying to install the CPU monitoring agent on a windows 8 machine, with node 0.11.8 and during the node-gyp rebuild I have the following error :
I a quite certain I have the right compiling tools to make node-gyp work. What is weird is that the builds seem to work with node 0.10.x version ( but the CPU profiling feature is not available on 0.10.x... )