npm run install-all fails on child_pty build on OSX El Capitan 10.11 Beta (15A278b) #27
Comments
|
for me its not fixed when using most recent cmd line tools. black-screen cf88802 |
|
I'm seeing the same error as @fibric but on |
|
Seeing this as well, same specs as @mdeland |
|
I had this issue, I switched from io.js to node and it was resolved. node-gyp doesn't play nicely with io.js |
|
confirmed! that did fix the problem for me. |
|
will be interesting to see what will happen when node v4.0 is released this month. because 4.0 is nothing else than io.js v3 :) |
|
Fails on 10.10.5 as well: 0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/iojs',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'run',
1 verbose cli 'install-all' ]
2 info using npm@2.13.3
3 info using node@v3.1.0
4 verbose run-script [ 'preinstall-all', 'install-all', 'postinstall-all' ]
5 info preinstall-all black-screen@0.0.1
6 info install-all black-screen@0.0.1
7 verbose unsafe-perm in lifecycle true
8 info black-screen@0.0.1 Failed to exec install-all script
9 verbose stack Error: black-screen@0.0.1 install-all: `rm -rf node_modules && npm install && bower install && npm run rebuild-pty`
9 verbose stack Exit status 1
9 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:214:16)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at EventEmitter.emit (events.js:172:7)
9 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at ChildProcess.emit (events.js:172:7)
9 verbose stack at maybeClose (internal/child_process.js:764:16)
9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
10 verbose pkgid black-screen@0.0.1
11 verbose cwd /Users/rasmus/src2/black-screen
12 error Darwin 14.5.0
13 error argv "/usr/local/bin/iojs" "/usr/local/bin/npm" "run" "install-all"
14 error node v3.1.0
15 error npm v2.13.3
16 error code ELIFECYCLE
17 error black-screen@0.0.1 install-all: `rm -rf node_modules && npm install && bower install && npm run rebuild-pty`
17 error Exit status 1
18 error Failed at the black-screen@0.0.1 install-all script 'rm -rf node_modules && npm install && bower install && npm run rebuild-pty'.
18 error This is most likely a problem with the black-screen package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error rm -rf node_modules && npm install && bower install && npm run rebuild-pty
18 error You can get their info via:
18 error npm owner ls black-screen
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]uname -a: MacBookPro11,2 |
|
Same Issue here - OSX El Capitan 10.11 Beta @fibric @rsms - The following workaround got the build working for me |
|
@joshtoo that xcode switch doesn't solve that for me. now i'm getting slidly different error message. i can have only xcode-beta running on 10.11 |
|
xcode-select only affects xcode builds and I hope there are no xcode projects involved in building this node package. The child_pty extension fails to build for me with a bunch of programmer+config errors like these: In file included from ../src/pty.cpp:1:
../node_modules/nan/nan.h:324:27: error: redefinition of 'NanEnsureHandleOrPersistent'
NAN_INLINE v8::Local<T> NanEnsureHandleOrPersistent(const v8::Local<T> &val) {
^
../node_modules/nan/nan.h:319:17: note: previous definition is here
v8::Handle<T> NanEnsureHandleOrPersistent(const v8::Handle<T> &val) {Complete output from building child_pty: https://gist.github.com/rsms/447eb864235f6364f297 |
|
The issues are with a convenience package called "nan", used by child_pty: https://github.com/nodejs/nan The version used by child_pty appears to be quite different from what I see in the current repo master. What a mess. (And child_pty is really simple shouldn't need the "nan" abstraction thingy.) |
|
@rsms - Hence why I called it an workaround. node-gyp rebuild was throwing the build error with Xcode pointing at xcode-select -switch to the path above changes the xcode command line tools location to So while I completely agree it "shouldn't" matter, it does temporarily move me past the build issue. |
|
@rsms, I was having similar issues with |
|
@Mattfxyz how did you switch to node from io? I'm getting the same error but i'm pretty sure i never switched from node to io.js |
|
Hmm, yeah still having this issue and I have node 0.10x on my machine. Never installed IO |
|
@sg-s OT, but io.js used to be a separate project, so you'd have iojs and/or nodejs installed. Recently iojs merged back into node (it was a branch of node to begin with.) So don't worry about it. The issue here seems to be a possibly broken and obviously very complex dependency tree where the current solution is to use a specific compiler (Apple's most recent clang build.) The authors might consider checking the compiler when running the install script to abort and prompt the user about the limitation, would a different clang be chosen by gyp. |
|
@rsms thanks! i figured so, reading the rest of the thread. |
|
Hey, guys. Please try to install it with the latest master. Note that the install command has changed from |
|
@ShockOne thanks, works. i had to install bower though. |
|
@sg-s will fix the bower issue in a moment. |
|
Now it works with iojs 3.3.0 |
|
it also installs on node v4.0 |
|
|
ghost
mentioned this issue
|
Same Issue here npm ERR! Darwin 15.0.0 |
I managed to fix it already and creating this issue just in case if somebody else will face it. This is fixed by installing latest command line tools from here https://developer.apple.com/downloads/ (at the moment of reporting this issue it was Command Line Tools OS X 10.11 for Xcode 7 beta 6)
The text was updated successfully, but these errors were encountered: