NEWS
Install-Fehler node_red Adapter
-
Hi,
beim Versuch den node_red-Adapter zu installieren gab es scheinbar Probleme zwei (optionale?) Module zu bauen:
` > 2016-05-23 23:14:44.737 - ESC[32minfoESC[39m: iobroker In file included from ../src/bcrypt_node.cc:1:0:../node_modules/nan/nan.h:592:20: er
ror: variable or field ‘AddGCEpilogueCallback’ declared void
v8::Isolate::GCEpilogueCallback callback
^
2016-05-23 23:14:44.753 - ESC[32minfoESC[39m: iobroker ../node_modules/nan/nan.h:592:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8:
:Isolate’ v8::Isolate::GCEpilogueCallback callback
^
../node_modules/nan/nan.h:593:18: error: expected primary-expression before ‘gc_type_filter’
, v8::GCType gc_type_filter = v8::kGCTypeAll) {
^
../node_modules/nan/nan.h:598:20: error: variable or field ‘RemoveGCEpilogueCallback’ declared void
v8::Isolate::GCEpilogueCallback callback) {
^
../node_modules/nan/nan.h:598:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
v8::Isolate::GCEpilogueCallback callback) {
^
../node_modules/nan/nan.h:603:20: error: variable or field ‘AddGCPrologueCallback’ declared void
v8::Isolate::GCPrologueCallback callback
^
../node_modules/nan/nan.h:603:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
v8::Isolate::GCPrologueCallback callback
^
../node_modules/nan/nan.h:604:18: error: expected primary-expression before ‘gc_type_filter’
, v8::GCType gc_type_filter = v8::kGCTypeAll) {
^
../node_modules/nan/nan.h:609:20: error: variable or field ‘RemoveGCPrologueCallback’ declared void
v8::Isolate::GCPrologueCallback callback) {
^
../node_modules/nan/nan.h:609:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
v8::Isolate::GCPrologueCallback callback) {
^
2016-05-23 23:14:46.664 - ESC[32minfoESC[39m: host.cubietruck instance system.adapter.admin.1 started with pid 2531
2016-05-23 23:14:54.206 - ESC[32minfoESC[39m: iobroker make: *** [Release/obj.target/bcrypt_lib/src/bcrypt_node.o] Error 1
2016-05-23 23:14:54.231 - ESC[32minfoESC[39m: iobroker gyp
2016-05-23 23:14:54.245 - ESC[32minfoESC[39m: iobroker
2016-05-23 23:14:54.258 - ESC[32minfoESC[39m: iobroker ERR!
2016-05-23 23:14:54.291 - ESC[32minfoESC[39m: iobroker build error
2016-05-23 23:14:54.353 - ESC[32minfoESC[39m: iobroker gyp ERR!
2016-05-23 23:14:54.360 - ESC[32minfoESC[39m: iobroker stack Error:
makefailed with exit code: 22016-05-23 23:14:54.389 - ESC[32minfoESC[39m: iobroker gyp ERR! stack at ChildProcess.onExit (/opt/iobroker/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
2016-05-23 23:14:54.400 - ESC[32minfoESC[39m: iobroker gyp ERR! stack at emitTwo (events.js:106:13)gyp ERR! stack at ChildProcess.emit (events.js:191:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System
2016-05-23 23:14:54.420 - ESC[32minfoESC[39m: iobroker Linux 4.5.2-sunxi
2016-05-23 23:14:54.431 - ESC[32minfoESC[39m: iobroker gyp ERR! command "/usr/bin/nodejs" "/opt/iobroker/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/node_modules/bcrypt
gyp ERR! node -v v6.2.0
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
2016-05-23 23:14:54.460 - ESC[32minfoESC[39m: iobroker
2016-05-23 23:14:54.571 - ESC[32minfoESC[39m: iobroker npm
2016-05-23 23:14:54.580 - ESC[32minfoESC[39m: iobroker
2016-05-23 23:14:54.602 - ESC[32minfoESC[39m: iobroker WARN deprecated i18next-client@1.10.3: you can use npm install i18next from version 2.0.0
2016-05-23 23:15:19.862 - ESC[32minfoESC[39m: iobroker npm WARN optional dep failed, continuing bcrypt@0.8.5
2016-05-23 23:15:27.975 - ESC[32minfoESC[39m: host.cubietruck instance system.adapter.admin.1 started with pid 2637
2016-05-23 23:15:37.490 - ESC[32minfoESC[39m: admin.1 starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.admin
2016-05-23 23:15:37.910 - ESC[32minfoESC[39m: admin.1 requesting all states
2016-05-23 23:15:37.921 - ESC[32minfoESC[39m: admin.1 requesting all objects
2016-05-23 23:15:37.927 - ESC[32minfoESC[39m: admin.1 Request actual repository…
2016-05-23 23:15:38.148 - ESC[31merrorESC[39m: admin.1 port 8081 already in use
2016-05-23 23:15:38.855 - ESC[31merrorESC[39m: host.cubietruck instance system.adapter.admin.1 terminated with code 1 ()
2016-05-23 23:15:38.857 - ESC[32minfoESC[39m: host.cubietruck Restart adapter system.adapter.admin.1 because enabled
2016-05-23 23:16:01.181 - ESC[32minfoESC[39m: iobroker In file included from ../src/serialport.h:5:0, from ../src/serialport.cpp:3:
../node_modules/nan/nan.h:590:20: error: variable or field ‘AddGCEpilogueCallback’ declared void
v8::Isolate::GCEpilogueCallback callback
^
../node_modules/nan/nan.h:590:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
v8::Isolate::GCEpilogueCallback callback
^
../node_modules/nan/nan.h:591:18: error: expected primary-expression before ‘gc_type_filter’
, v8::GCType gc_type_filter = v8::kGCTypeAll) {
^
../node_modules/nan/nan.h:596:20: error: variable or field ‘RemoveGCEpilogueCallback’ declared void
v8::Isolate::GCEpilogueCallback callback) {
^
2016-05-23 23:16:01.195 - ESC[32minfoESC[39m: iobroker ../node_modules/nan/nan.h:596:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’ v8::Isolate::GCEpilogueCallback callback) {
^
../node_modules/nan/nan.h:601:20: error: variable or field ‘AddGCPrologueCallback’ declared void
v8::Isolate::GCPrologueCallback callback
^
../node_modules/nan/nan.h:601:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
v8::Isolate::GCPrologueCallback callback
^
../node_modules/nan/nan.h:602:18: error: expected primary-expression before ‘gc_type_filter’
, v8::GCType gc_type_filter = v8::kGCTypeAll) {
^
../node_modules/nan/nan.h:607:20: error: variable or field ‘RemoveGCPrologueCallback’ declared void
v8::Isolate::GCPrologueCallback callback) {
v8::Isolate::GCPrologueCallback callback) {
^
2016-05-23 23:16:02.123 - ESC[32minfoESC[39m: iobroker make: *** [Release/obj.target/serialport/src/serialport.o] Error 1
2016-05-23 23:16:02.155 - ESC[32minfoESC[39m: iobroker gyp
2016-05-23 23:16:02.171 - ESC[32minfoESC[39m: iobroker
2016-05-23 23:16:02.179 - ESC[32minfoESC[39m: iobroker ERR! build error
2016-05-23 23:16:02.202 - ESC[32minfoESC[39m: iobroker gyp ERR! stack Error:
makefailed with exit code: 22016-05-23 23:16:02.210 - ESC[32minfoESC[39m: iobroker gyp ERR! stack at ChildProcess.onExit (/opt/iobroker/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
2016-05-23 23:16:02.230 - ESC[32minfoESC[39m: iobroker gyp ERR! stack at emitTwo (events.js:106:13)gyp ERR! stack at ChildProcess.emit (events.js:191:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Linux 4.5.2-sunxi
2016-05-23 23:16:02.257 - ESC[32minfoESC[39m: iobroker gyp ERR! command "/usr/bin/nodejs" "/opt/iobroker/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "–fallback-to-build" "--module=/opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/node_modules/node-red-node-serialport/node_modules/serialport/build/Release/node-v48-linux-arm/serialport.node" "--module_name=serialport" "--module_path=/opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/node_modules/node-red-node-serialport/node_modules/serialport/build/Release/node-v48-linux-arm"gyp ERR! cwd /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/node_modules/node-red-node-serialport/node_modules/serialport
gyp ERR! node -v v6.2.0
gyp ERR! node-gyp -v v3.3.1
gyp
2016-05-23 23:16:02.282 - ESC[32minfoESC[39m: iobroker ERR! not ok node-pre-gyp
2016-05-23 23:16:02.285 - ESC[32minfoESC[39m: iobroker ERR! build error
2016-05-23 23:16:02.325 - ESC[32minfoESC[39m: iobroker node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/nodejs /opt/iobroker/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/node_modules/node-red-node-serialport/node_modules/serialport/build/Release/node-v48-linux-arm/serialport.node --module_name=serialport --module_path=/opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/node_modules/node-red-node-serialport/node_modules/serialport/build/Release/node-v48-linux-arm' (1)
2016-05-23 23:16:02.342 - ESC[32minfoESC[39m: iobroker node-pre-gyp
2016-05-23 23:16:02.347 - ESC[32minfoESC[39m: iobroker ERR! stack at ChildProcess. <anonymous>(/opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/node_modules/node-red-node-serialport/node_modules/serialport/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
2016-05-23 23:16:02.356 - ESC[32minfoESC[39m: iobroker node-pre-gyp ERR! stack
2016-05-23 23:16:02.385 - ESC[32minfoESC[39m: iobroker at emitTwo (events.js:106:13)node-pre-gyp ERR! stack at ChildProcess.emit (events.js:191:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:850:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
node-pre-gyp ERR! System Linux 4.5.2-sunxi
node-pre-gyp ERR!
2016-05-23 23:16:02.398 - ESC[32minfoESC[39m: iobroker command "/usr/bin/nodejs" "/opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/node_modules/node-red-node-serialport/node_modules/serialport/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/node_modules/node-red-node-serialport/node_modules/serialport
node-pre-gyp ERR! node -v v6.2.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.18
node-pre-gyp ERR! not ok
2016-05-23 23:16:02.463 - ESC[32minfoESC[39m: iobroker npm WARN
2016-05-23 23:16:02.481 - ESC[32minfoESC[39m: iobroker optional dep failed, continuing node-red-node-serialport@0.1.2</anonymous> `
Kann man das ignorieren oder wie kann man es fixen?
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden