-
Notifications
You must be signed in to change notification settings - Fork 21
Description
I am getting below error while installing v8-debug, any ideas?
1035 info install v8-debug@0.3.1
1036 verbose unsafe-perm in lifecycle true
1037 info v8-debug@0.3.1 Failed to exec install script
1038 verbose unlock done using C:\Users\Nadav\AppData\Roaming\npm-cache_locks\v8-debug-6a84c2f0ebeb5635.lock for C:\Program Files\nodejs\node_modules\v8-debug
1039 verbose stack Error: v8-debug@0.3.1 install: node-pre-gyp install --fallback-to-build
1039 verbose stack Exit status 1
1039 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:212:16)
1039 verbose stack at EventEmitter.emit (events.js:98:17)
1039 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:14:12)
1039 verbose stack at ChildProcess.emit (events.js:98:17)
1039 verbose stack at maybeClose (child_process.js:766:16)
1039 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:833:5)
1040 verbose pkgid v8-debug@0.3.1
1041 verbose cwd C:\Program Files\nodejs
1042 error Windows_NT 6.2.9200
1043 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "v8-debug"
1044 error node v0.10.34
1045 error npm v2.1.16
1046 error code ELIFECYCLE
1047 error v8-debug@0.3.1 install: node-pre-gyp install --fallback-to-build
1047 error Exit status 1
1048 error Failed at the v8-debug@0.3.1 install script 'node-pre-gyp install --fallback-to-build'.
1048 error This is most likely a problem with the v8-debug package,
1048 error not with npm itself.
1048 error Tell the author that this fails on your system:
1048 error node-pre-gyp install --fallback-to-build
1048 error You can get their info via:
1048 error npm owner ls v8-debug
1048 error There is likely additional logging output above.
1049 verbose exit [ 1, true ]
1050 verbose unbuild node_modules\v8-debug
Activity
3y3 commentedon Dec 25, 2014
How about this issue? Is this helpful for you?
sparxHub commentedon Dec 26, 2014
Didn't solve my problem.
I saw node-gyp required VS2012, so I installed it and set the npm's config related, but still it doesn't work.
Do you think there is any relation to npm's version 2.1.16?
sparxHub commentedon Dec 28, 2014
I re-install nodejs and python to 32-bit version, and now it works. It seems like there some issues regarding 64-bit
ericchaves commentedon Jan 5, 2015
I'm facing the same trouble. @sparkGitHub could you share the steps you did to solve it?
3y3 commentedon Jan 9, 2015
I added some fixes to v8-profiler and v8-debug. Also I added prebuild binaries for Linux and OSX.
Please try to reinstall node-inspector now.
afreeland commentedon Feb 17, 2015
I am having this issue as well
I appear to be having a similar issue...any udpates?
CoreSoft2 commentedon Sep 17, 2015
Same issue here
pm ERR! Darwin 14.5.0
npm ERR! argv "node" "/usr/local/bin/npm" "update"
npm ERR! node v0.10.21
npm ERR! npm v2.11.3
npm ERR! code ELIFECYCLE
npm ERR! v8-debug@0.4.6 install:
node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the v8-debug@0.4.6 install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the v8-debug package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get their info via:
npm ERR! npm owner ls v8-debug
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
p1tt1 commentedon Sep 17, 2015
Same issue here
lhttjdr commentedon Sep 19, 2015
Same issue with v8-debug@0.4.6
pjcliche commentedon Sep 20, 2015
Same problem, but running on Debian. Here's the actual erroring out leading to the failure message :
CXX(target) Release/obj.target/debug/src/debug.o
In file included from ../src/debug.cc:2:0:
../node_modules/nan/nan.h:261:25: error: redefinition of 'template v8::Local NanEnsureLocal(v8::Local)'
NAN_INLINE v8::Local NanEnsureLocal(v8::Local val) {
^
../node_modules/nan/nan.h:256:25: note: 'template v8::Local NanEnsureLocal(v8::Handle)' previously declared here
NAN_INLINE v8::Local NanEnsureLocal(v8::Handle val) {
^
../node_modules/nan/nan.h:661:13: error: 'node::smalloc' has not been declared
, node::smalloc::FreeCallback callback
^
../node_modules/nan/nan.h:661:35: error: expected ',' or '...' before 'callback'
, node::smalloc::FreeCallback callback
^
../node_modules/nan/nan.h: In function 'v8::Localv8::Object NanNewBufferHandle(char, size_t, int)':
../node_modules/nan/nan.h:665:50: error: 'callback' was not declared in this scope
v8::Isolate::GetCurrent(), data, length, callback, hint);
^
../node_modules/nan/nan.h:665:60: error: 'hint' was not declared in this scope
v8::Isolate::GetCurrent(), data, length, callback, hint);
^
../node_modules/nan/nan.h: In function 'v8::Localv8::Object NanNewBufferHandle(const char, uint32_t)':
../node_modules/nan/nan.h:672:67: error: call of overloaded 'New(v8::Isolate, const char&, uint32_t&)' is ambiguous
return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);
^
../node_modules/nan/nan.h:672:67: note: candidates are:
In file included from ../node_modules/nan/nan.h:25:0,
from ../src/debug.cc:2:
/root/.node-gyp/4.0.0/include/node/node_buffer.h:31:40: note: v8::MaybeLocalv8::Object node::Buffer::New(v8::Isolate_, v8::Localv8::String, node::encoding)
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate_ isolate,
^
/root/.node-gyp/4.0.0/include/node/node_buffer.h:31:40: note: no known conversion for argument 3 from 'uint32_t {aka unsigned int}' to 'node::encoding'
/root/.node-gyp/4.0.0/include/node/node_buffer.h:43:40: note: v8::MaybeLocalv8::Object node::Buffer::New(v8::Isolate_, char_, size_t)
NODE_EXTERN v8::MaybeLocalv8::Object New(v8::Isolate* isolate,
^
/root/.node-gyp/4.0.0/include/node/node_buffer.h:43:40: note: no known conversion for argument 2 from 'const char_' to 'char_'
In file included from ../src/debug.cc:2:0:
../node_modules/nan/nan.h: In function 'v8::Localv8::Object NanNewBufferHandle(uint32_t)':
../node_modules/nan/nan.h:676:61: error: could not convert 'node::Buffer::New(v8::Isolate::GetCurrent(), ((size_t)size))' from 'v8::MaybeLocalv8::Object' to 'v8::Localv8::Object'
return node::Buffer::New(v8::Isolate::GetCurrent(), size);
^
../node_modules/nan/nan.h: In function 'v8::Localv8::Object NanBufferUse(char_, uint32_t)':
../node_modules/nan/nan.h:683:12: error: 'Use' is not a member of 'node::Buffer'
return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
^
../src/debug.cc: In static member function 'static void nodex::Debug::InternalConstructorName(const v8::FunctionCallbackInfov8::Value&)':
../src/debug.cc:194:23: warning: deprecated conversion from string constant to 'char_' [-Wwrite-strings]
result_type = "";
^
debug.target.mk:90: recipe for target 'Release/obj.target/debug/src/debug.o' failed
make: *** [Release/obj.target/debug/src/debug.o] Error 1
wpm commentedon Sep 21, 2015
I'm seeing the same thing when I try to build the default Yeoman angular-fullstack.
node-pre-gyp 0.6.10, Node 4.1.0, OS X 10.10.5
jamescalhoun commentedon Sep 22, 2015
I also am seeing this issue when I try to run npm install using Yeoman angular-fullstack
Errors start at:
CXX(target) Release/obj.target/debug/src/debug.o
In file included from ../src/debug.cc:2:
../../../../nan/nan.h:261:25: error: redefinition of '_NanEnsureLocal'
NAN_INLINE v8::Local _NanEnsureLocal(v8::Local val) {
then...
1 warning and 10 errors generated.
make: *** [Release/obj.target/debug/src/debug.o] Error 1
gyp ERR! build error
gyp ERR! stack Error:
make
failed with exit code: 2gyp ERR! stack at ChildProcess.onExit (/Users/[edited]/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "/usr/local/bin/node" "/Users/[edited]/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/[edited]/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64/debug.node" "--module_name=debug" "--module_path=/Users/[edited]/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64"
gyp ERR! cwd /Users/[edited]/node_modules/node-inspector/node_modules/v8-debug
gyp ERR! node -v v4.1.0
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /Users/[edited]/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/[edited]/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64/debug.node --module_name=debug --module_path=/[edited]/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.4.6/node-v46-darwin-x64' (1)
node-pre-gyp ERR! stack at ChildProcess. (/Users/[edited]/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:817:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
node-pre-gyp ERR! System Darwin 14.5.0
node-pre-gyp ERR! command "/usr/local/bin/node" "/Users/[edited]/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/[edited]/node_modules/node-inspector/node_modules/v8-debug
node-pre-gyp ERR! node -v v4.1.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.10
node-pre-gyp ERR! not ok
and end with
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.1.0
npm ERR! npm v3.3.4
npm ERR! code ELIFECYCLE
npm ERR! v8-debug@0.4.6 install:
node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the v8-debug@0.4.6 install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the v8-debug package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
3y3 commentedon Sep 22, 2015
The problem is in grunt-node-inspector, which was linked to outdated node-inspector version.
Can anyone call
grunt-node-inspector
maintainer to approve on a pr which bumpsnode-inspector
version?remydavid commentedon Oct 1, 2015
Same problem for me, solved by npm install -g grunt-node-inspector, which installs the latest version (0.3.0) which doesn't seems to have the problem.
62 remaining items
hatinfotech commentedon Aug 7, 2017
I was resolved my problem by install package in native console, install via ssh terminal was not wokrked.
alarv commentedon Sep 12, 2017
Downgrading node to
v6.9.1
worked for meshivarajnaidu commentedon Sep 18, 2017
Any Other Solution ?? I Want to install for Node v8.x
ashishyadav23 commentedon Nov 9, 2017
thanks @russfrisch +1 its work for me also
chucklu commentedon May 28, 2018
After checking the FAQ of node-pre-gyp, I might need to install the C++ runtime. I am installing it now and give feedback here tomorrow.
Frequently Ask Questions about node-pre-gyp
On Windows for Node C++ modules that do not link external libraries there are no major gotchas. The binaries you build will work well on any Windows system. This is because the default linking for Node is /MT (aka RuntimeLibrary:0) and node-pre-gyp modules inherit this setting by default. So, the C++ runtime will be statically linked into the addon binary and therefore you don't need to worry about your users installing it separately.
However, for Node C++ modules on Windows that depend on external shared libraries, you'll need to understand whether those libraries were linked with /MD or /MT. If the external DLL was linked with /MD then you'll likely need to also link your Node C++ addon using /MD and you'll need to ensure that your users have the right C++ runtime installed for your addon binary to work. For example, if you compiled your binary with Visual Studio 2013 then your users would need This "C++ Redistributable".
chucklu commentedon May 28, 2018
I am not sure why the proxy is invalid, I already configured the proxy as https://stackoverflow.com/questions/40171953/node-npm-proxy-authentication-how-do-i-configure-it. It's just a warning.
And the error is :
Anyone knows something about this? @russfrisch
chucklu commentedon May 29, 2018
Someone has submit an issue in node-inspector already
node-inspector/node-inspector#1041
zhaoyongjiang commentedon May 31, 2018
@antharamshivakumar Is the problem solved? My computer is the macmini。I need your help。thanks a lot
chucklu commentedon Jun 1, 2018
@zhaoyongjiang No, I gave up. And I find the following message for node-inspector
I decide to use the built-in debugger in Node.js .
smdpro commentedon Sep 18, 2018
@russfrisch +1 worked for me
zhaoyongjiang commentedon Sep 18, 2018
@chucklu thanks a lot
tommyyama2020 commentedon Apr 9, 2020
anybody encountering the same in the latest ubuntu ? i changed to ">=" as suggested here. But it failed.
kenliten commentedon Oct 22, 2020
I'm on OpenSUSE and for me, nothing here is working.
I'm having the same error and the same with Linux mint, anyone knows another way to make it works?