Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

latest npm, python 2.7.x, not installing #2

Closed
ghost opened this issue Mar 20, 2015 · 3 comments
Closed

latest npm, python 2.7.x, not installing #2

ghost opened this issue Mar 20, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Mar 20, 2015

219 verbose stack Error: bufferutil@1.0.1 install: node-gyp rebuild
219 verbose stack Exit status 1
219 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:213:16)
219 verbose stack at EventEmitter.emit (events.js:110:17)
219 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:14:12)
219 verbose stack at ChildProcess.emit (events.js:110:17)
219 verbose stack at maybeClose (child_process.js:1008:16)
219 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1080:5)
220 verbose pkgid bufferutil@1.0.1
221 verbose cwd D:\CodeRoot\OpSuite\OpSuite\OpSuiteDev\Website\OpSuite.MobilePOS
222 error Windows_NT 6.1.7601
223 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "bufferutil"
224 error node v0.12.0
225 error npm v2.7.3
226 error code ELIFECYCLE
227 error bufferutil@1.0.1 install: node-gyp rebuild
227 error Exit status 1
228 error Failed at the bufferutil@1.0.1 install script 'node-gyp rebuild'.
228 error This is most likely a problem with the bufferutil package,
228 error not with npm itself.
228 error Tell the author that this fails on your system:
228 error node-gyp rebuild
228 error You can get their info via:
228 error npm owner ls bufferutil
228 error There is likely additional logging output above.
229 verbose exit [ 1, true ]
230 verbose unbuild node_modules\bufferutil
231 info preuninstall bufferutil@1.0.1
232 info uninstall bufferutil@1.0.1

@felicienfrancois
Copy link

I got the same issue (iojs 1.6.2, npm 2.7.1, python 2.7.9)

> bufferutil@1.0.1 install ...\node_modules\ws\node_modules\bufferutil
> node-gyp rebuild

..\node_modules\ws\node_modules\bufferutil>if not defined npm_config_node_gyp (node "c:\Program Files\iojs\node_modules\
npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (rebuild)
child_process: customFds option is deprecated, use stdio instead.
Génération des projets individuellement dans cette solution. Pour activer la génération en parallèle, ajoutez le commutateur "/m".
MSBUILD : error MSB3428: Impossible de charger le composant Visual C++ "VCBuild.exe". Pour corriger le problème, vous devez 1) installer le Kit de dé
veloppement .NET Framework 2.0 SDK, 2) installer Microsoft Visual Studio 2005 ou 3) ajouter l'emplacement du composant au chemin d'accès système, s'i
l est installé ailleurs.  [...\node_modules\ws\node_modules\bufferutil\build\binding.sln]

gyp ERR! build error
gyp ERR! stack Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (c:\Program Files\iojs\node_modules\npm\node_modules\node-gyp\lib\build.js:267:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:169:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1044:12)
gyp ERR! System Windows_NT 6.3.9600
gyp ERR! command "c:\\Program Files\\iojs\\node.exe" "c:\\Program Files\\iojs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd ...\node_modules\ws\node_modules\bufferutil
gyp ERR! node -v v1.6.2
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok

@ghost
Copy link
Author

ghost commented Apr 8, 2015

I ended up re-installing the latested node. fixed my problem.

@ghost ghost closed this as completed Apr 8, 2015
@doivosevic
Copy link

Reinstalling node also fixed this for me although I did have a pretty fresh install of node. Windows 8.1

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants