node-serialport: binding file could not be found

If i start my app including serialport var sp = require('serialport').SerialPort; i get an error from bindings that the bindings file could not be found. Is there a configuration error? It’s a fresh install.

xxx@ubuntu:~/Arbeitsfläche/node/firstapp$ node app

node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: Could not load the bindings file. Tried:
 -> /home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/build/Debug/serialport.node
 -> /home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/build/Release/serialport.node
 -> /home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/out/Debug/serialport.node
 -> /home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/Debug/serialport.node
 -> /home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/out/Release/serialport.node
 -> /home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/Release/serialport.node
 -> /home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/build/default/serialport.node
 -> /home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/compiled/0.6/linux/ia32/serialport.node
    at bindings (/home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/node_modules/bindings/bindings.js:82:13)
    at Object.<anonymous> (/home/xxx/Arbeitsfläche/node/firstapp/node_modules/serialport/serialport.js:7:44)
    at Module._compile (module.js:441:26)
    at Object..js (module.js:459:10)
    at Module.load (module.js:348:32)
    at Function._load (module.js:308:12)
    at Module.require (module.js:354:17)
    at require (module.js:370:17)
    at Object.<anonymous> (/home/xxx/Arbeitsfläche/node/firstapp/app.js:20:10)
    at Module._compile (module.js:441:26)

About this issue

  • Original URL
  • State: closed
  • Created 12 years ago
  • Comments: 15 (3 by maintainers)

Most upvoted comments

Can you try opening a terminal to node_modules/serialport and run “node-gyp configure build”. This might be a similar problem to pull request #65 which hasn’t been published to npm yet.