node-inspector / v8-debug

v8 debugger extending API
BSD 2-Clause "Simplified" License
44 stars 21 forks source link

node-pre-gyp install --fallback-to-build #7

Open sparxHub opened 9 years ago

sparxHub commented 9 years ago

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

3y3 commented 9 years ago

How about this issue? Is this helpful for you?

sparxHub commented 9 years ago

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 commented 9 years ago

I re-install nodejs and python to 32-bit version, and now it works. It seems like there some issues regarding 64-bit

ericchaves commented 9 years ago

I'm facing the same trouble. @SparkGithub could you share the steps you did to solve it?

3y3 commented 9 years ago

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 commented 9 years ago

I am having this issue as well

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program Files (
x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "node-inspector
"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE

npm ERR! v8-debug@0.3.5 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the v8-debug@0.3.5 install script 'node-pre-gyp install --fal
lback-to-build'.
npm ERR! This is most likely a problem with the v8-debug package,
npm ERR! not with npm itself.

I appear to be having a similar issue...any udpates?

CoreSoft2 commented 9 years ago

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 commented 9 years ago

Same issue here

lhttjdr commented 9 years ago

Same issue with v8-debug@0.4.6

pjcliche commented 9 years ago

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 ^ ../nodemodules/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); ^ ../nodemodules/nan/nan.h: In function 'v8::Localv8::Object NanNewBufferHandle(const char, uint32_t)': ../nodemodules/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/nodebuffer.h:31:40: note: v8::MaybeLocalv8::Object node::Buffer::New(v8::Isolate, v8::Localv8::String, node::encoding) NODEEXTERN 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/nodebuffer.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/nodebuffer.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); ^ ../nodemodules/nan/nan.h: In function 'v8::Localv8::Object NanBufferUse(char, uint32_t)': ../nodemodules/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 commented 9 years ago

I'm seeing the same thing when I try to build the default Yeoman angular-fullstack.

node-pre-gyp ERR! stack Error: Failed to execute 'node-gyp build --fallback-to-build --module=/Users/williammcneill/Documents/Work/QA/devenv/src/cloudhammer/node_modules/grunt-node-inspector/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/williammcneill/Documents/Work/QA/devenv/src/cloudhammer/node_modules/grunt-node-inspector/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.<anonymous> (/Users/williammcneill/Documents/Work/QA/devenv/src/cloudhammer/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/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/Cellar/node/4.1.0/bin/node" "/Users/williammcneill/Documents/Work/QA/devenv/src/cloudhammer/node_modules/grunt-node-inspector/node_modules/node-inspector/node_modules/v8-debug/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/williammcneill/Documents/Work/QA/devenv/src/cloudhammer/node_modules/grunt-node-inspector/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 

node-pre-gyp 0.6.10, Node 4.1.0, OS X 10.10.5

jamescalhoun commented 9 years ago

I also am seeing this issue when I try to run npm install using Yeoman angular-fullstack

Errors start at:

v8-debug@0.4.6 install /Users/[edited]/node_modules/node-inspector/node_modules/v8-debug node-pre-gyp install --fallback-to-build

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: 2 gyp 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 commented 9 years ago

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 bumps node-inspector version?

remydavid commented 9 years ago

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.

hanssl commented 9 years ago

I am getting the same "Failed at the v8-debug@0.4.6 install script 'node-pre-gyp install --fallback-to-build'." error. I have tried rolling npm back to v2, that did not fix it. I have tried the suggestion above 'npm install -g grunt-node-inspector' but that did not fix the issue.

3y3 commented 9 years ago

@hanssl , grunt-node-inspector already updated and uses correct v8-debug version. Where you found outdated grunt-node-inspector?

Maybe npm cache clean will be helpful for you?

hanssl commented 9 years ago

I have tried ‘npm cache clean’ with ‘bower cache clean’ many times. Problem persists.

I have attached my npm log.

On Oct 27, 2015, at 5:33 PM, Yury Puzynya notifications@github.com wrote:

npm cache clean

fcagalj commented 9 years ago

Does this have any sense: "opened this issue on Dec 25, 2014"????

I leave Windows hoping to avoid this issues, after spending ages on node-gyp nonsenses.

So now I need to spend week to make PR to grunt-node-inspector and hope somebody will accept in order to use it until next bug appear?

lukeyxu commented 9 years ago

npm ERR! Linux 3.13.0-57-generic npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "grunt-node-inspector" npm ERR! node v5.0.0 npm ERR! npm v3.3.10 npm ERR! code ELIFECYCLE

npm ERR! v8-debug@0.5.4 install: node-pre-gyp install --fallback-to-build npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the v8-debug@0.5.4 install script 'node-pre-gyp install --fallback-to-build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, 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.

Same issue here, I'm running ubuntu.

fcagalj commented 9 years ago

Rollback to node 4.2.2 solved problems for me on Ubuntu 14.04.

yves-s commented 9 years ago

I was on node 5, rolled back to node 4.2.2 but still the same error. I'm on OSx 10.11.

In my case the issue happens with angular-fullstack as well or rather npm install

Any new insights?

russfrisch commented 9 years ago

I was experiencing this same issue. Changing in the version for grunt-node-inspector to prepend a ">=" instead of a "~" got this to work for me.

yves-s commented 9 years ago

@russfrisch worked for me as well, thx

marfago commented 9 years ago

@russfrisch worked for me as well on Node 0.12.7. Thank you.

surprisetalk commented 9 years ago

I encountered the same problem when trying to install meanjs with nodejs@4.2.2 and npm@2.14.10. Going into the package.json (in the cloned meanjs repo) and changing

"grunt-node-inspector": "~0.2.0"

to

"grunt-node-inspector": ">=0.2.0",

did the trick.

Thanks @russfrisch !

srabeeh commented 9 years ago

Thanks @russfrisch

dam1 commented 9 years ago

You can also update the package.json to

    "grunt-node-inspector": "^0.4.1",
tgwhite commented 9 years ago

Was having same error on windows and ubuntu after I rage-quit windows. Also using the angular-fullstack generator. @russfrisch fix worked like a charm in ubuntu 14.04 -- will report back if it works in windows.

EDIT: ALSO WORKS ON WINDOWS :)

adityareddy commented 8 years ago

+1 Thanks @russfrisch

g1eb commented 8 years ago

@russfrisch +1

lazaropj commented 8 years ago

@russfrisch +1

bownie commented 8 years ago

Wow @russfrisch +1 - indeed this also works for Windows. Also had this problem using the angular fullstack generator and originally came via this issue https://github.com/nodejs/node-gyp/issues/629

ghost commented 8 years ago

@russfrisch +1

jackkum commented 8 years ago

@surprisetalk :+1:

d46 commented 8 years ago

@russfrisch +1

FingersCrossed commented 8 years ago

@russfrisch +1

bastianwegge commented 8 years ago

@russfrisch +1 !!!

jquigley1003 commented 8 years ago

Thanks for your solution @russfrisch +1 !!!

ryanooi commented 8 years ago

@russfrisch +1

ghost commented 8 years ago

@russfrisch Thanks!

Aabir1 commented 8 years ago

i am not able to use this => sudo yo meanjs:crud-module costomers. please help me . i am stuck from yesturday

surprisetalk commented 8 years ago

@Aabir1 I think meanjs:crud-module has been removed from the newer version of Yo. Use yo --help and then see if it appears under "Available Generators". I know sudo yo meanjs:mean-module customers will work, but it will not do quite what meanjs:crud-module used to do. Best of luck.

goran-blazin commented 8 years ago

@russfrisch +1 Thanks :)

colwilson commented 8 years ago

Thanks @russfrisch that fixed it for me +1

burakkilic commented 8 years ago

+1 @russfrisch thank you

HdSeKenny commented 8 years ago

@Can anyone tell me where can i find that package.json, which package.json. @burakkilic

kinzhao commented 8 years ago

@SHEFFKUAN it should be located where you root directory is. Example: project_folder/package.json

chandruk4321 commented 8 years ago

@russfrisch +1

chusri commented 8 years ago

@russfrisch +1 it's work

hsgfan commented 8 years ago

+1