Last active
November 20, 2017 20:35
-
-
Save ancienthero/16f801d83d871b1e0b8997d0b386146a to your computer and use it in GitHub Desktop.
espruino-cli log
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
npm i -g espruino-cli | |
/usr/local/bin/esp -> /usr/local/lib/node_modules/espruino-cli/bin/esp.js | |
> serialport@1.2.5 install /usr/local/lib/node_modules/espruino-cli/node_modules/serialport | |
> node-gyp rebuild | |
CXX(target) Release/obj.target/serialport/src/serialport.o | |
In file included from ../src/serialport.cpp:3: | |
../src/serialport.h:30:34: error: no type named 'Arguments' in namespace 'v8'; did you mean 'v8::internal::Arguments'? | |
v8::Handle<v8::Value> List(const v8::Arguments& args); | |
^~~~~~~~~~~~~ | |
v8::internal::Arguments | |
/Users/pawel/.node-gyp/9.1.0/include/node/v8.h:141:7: note: 'v8::internal::Arguments' declared here | |
class Arguments; | |
^ | |
In file included from ../src/serialport.cpp:3: | |
../src/serialport.h:31:15: error: unknown type name 'uv_work_t' | |
void EIO_List(uv_work_t* req); | |
^ | |
../src/serialport.h:32:20: error: unknown type name 'uv_work_t' | |
void EIO_AfterList(uv_work_t* req); | |
^ | |
../src/serialport.h:34:34: error: no type named 'Arguments' in namespace 'v8'; did you mean 'v8::internal::Arguments'? | |
v8::Handle<v8::Value> Open(const v8::Arguments& args); | |
^~~~~~~~~~~~~ | |
v8::internal::Arguments | |
/Users/pawel/.node-gyp/9.1.0/include/node/v8.h:141:7: note: 'v8::internal::Arguments' declared here | |
class Arguments; | |
^ | |
In file included from ../src/serialport.cpp:3: | |
../src/serialport.h:35:15: error: unknown type name 'uv_work_t' | |
void EIO_Open(uv_work_t* req); | |
^ | |
../src/serialport.h:36:20: error: unknown type name 'uv_work_t' | |
void EIO_AfterOpen(uv_work_t* req); | |
^ | |
../src/serialport.h:39:35: error: no type named 'Arguments' in namespace 'v8'; did you mean 'v8::internal::Arguments'? | |
v8::Handle<v8::Value> Write(const v8::Arguments& args); | |
^~~~~~~~~~~~~ | |
v8::internal::Arguments | |
/Users/pawel/.node-gyp/9.1.0/include/node/v8.h:141:7: note: 'v8::internal::Arguments' declared here | |
class Arguments; | |
^ | |
In file included from ../src/serialport.cpp:3: | |
../src/serialport.h:40:16: error: unknown type name 'uv_work_t' | |
void EIO_Write(uv_work_t* req); | |
^ | |
../src/serialport.h:41:21: error: unknown type name 'uv_work_t' | |
void EIO_AfterWrite(uv_work_t* req); | |
^ | |
../src/serialport.h:43:35: error: no type named 'Arguments' in namespace 'v8'; did you mean 'v8::internal::Arguments'? | |
v8::Handle<v8::Value> Close(const v8::Arguments& args); | |
^~~~~~~~~~~~~ | |
v8::internal::Arguments | |
/Users/pawel/.node-gyp/9.1.0/include/node/v8.h:141:7: note: 'v8::internal::Arguments' declared here | |
class Arguments; | |
^ | |
In file included from ../src/serialport.cpp:3: | |
../src/serialport.h:44:16: error: unknown type name 'uv_work_t' | |
void EIO_Close(uv_work_t* req); | |
^ | |
../src/serialport.h:45:21: error: unknown type name 'uv_work_t' | |
void EIO_AfterClose(uv_work_t* req); | |
^ | |
../src/serialport.h:47:35: error: no type named 'Arguments' in namespace 'v8'; did you mean 'v8::internal::Arguments'? | |
v8::Handle<v8::Value> Flush(const v8::Arguments& args); | |
^~~~~~~~~~~~~ | |
v8::internal::Arguments | |
/Users/pawel/.node-gyp/9.1.0/include/node/v8.h:141:7: note: 'v8::internal::Arguments' declared here | |
class Arguments; | |
^ | |
In file included from ../src/serialport.cpp:3: | |
../src/serialport.h:48:16: error: unknown type name 'uv_work_t' | |
void EIO_Flush(uv_work_t* req); | |
^ | |
../src/serialport.h:49:21: error: unknown type name 'uv_work_t' | |
void EIO_AfterFlush(uv_work_t* req); | |
^ | |
../src/serialport.h:89:3: error: unknown type name 'uv_work_t' | |
uv_work_t req; | |
^ | |
../src/serialport.h:90:3: error: unknown type name 'ngx_queue_t' | |
ngx_queue_t queue; | |
^ | |
In file included from ../src/serialport.cpp:8: | |
../src/serialport_poller.h:10:39: error: expected class name | |
class SerialportPoller : public node::ObjectWrap { | |
^ | |
../src/serialport_poller.h:23:42: error: no type named 'Arguments' in namespace 'v8'; did you mean 'v8::internal::Arguments'? | |
static v8::Handle<v8::Value> New(const v8::Arguments& args); | |
^~~~~~~~~~~~~ | |
v8::internal::Arguments | |
/Users/pawel/.node-gyp/9.1.0/include/node/v8.h:141:7: note: 'v8::internal::Arguments' declared here | |
class Arguments; | |
^ | |
fatal error: too many errors emitted, stopping now [-ferror-limit=] | |
20 errors generated. | |
make: *** [Release/obj.target/serialport/src/serialport.o] Error 1 | |
gyp ERR! build error | |
gyp ERR! stack Error: `make` failed with exit code: 2 | |
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23) | |
gyp ERR! stack at emitTwo (events.js:135:13) | |
gyp ERR! stack at ChildProcess.emit (events.js:224:7) | |
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12) | |
gyp ERR! System Darwin 17.2.0 | |
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" | |
gyp ERR! cwd /usr/local/lib/node_modules/espruino-cli/node_modules/serialport | |
gyp ERR! node -v v9.1.0 | |
gyp ERR! node-gyp -v v3.6.2 | |
gyp ERR! not ok | |
npm WARN EINVAL: invalid argument, rmdir '/usr/local/lib/node_modules/espruino-cli/node_modules/serialport/build/Release/.deps/Release/obj.target/serialport/src' | |
npm ERR! code ELIFECYCLE | |
npm ERR! errno 1 | |
npm ERR! serialport@1.2.5 install: `node-gyp rebuild` | |
npm ERR! Exit status 1 | |
npm ERR! | |
npm ERR! Failed at the serialport@1.2.5 install script. | |
npm ERR! This is probably not a problem with npm. There is likely additional logging output above. | |
npm ERR! A complete log of this run can be found in: | |
npm ERR! /Users/pawel/.npm/_logs/2017-11-20T19_59_03_308Z-debug.log |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment