t2-cli: Pre-compiled module is missing: midi and `Could not locate the bindings file`

I’m trying to use the node-midi package and I’m getting the Pre-compiled module is missing: midi. warning when running t2 run index.js. That doesn’t stop the build, but it eventually fails with

Error: Could not locate the bindings file. Tried:
 → /tmp/remote-script/node_modules/midi/build/midi.node
 → /tmp/remote-script/node_modules/midi/build/Debug/midi.node
 → /tmp/remote-script/node_modules/midi/build/Release/midi.node
 → /tmp/remote-script/node_modules/midi/out/Debug/midi.node
 → /tmp/remote-script/node_modules/midi/Debug/midi.node
 → /tmp/remote-script/node_modules/midi/out/Release/midi.node
 → /tmp/remote-script/node_modules/midi/Release/midi.node
 → /tmp/remote-script/node_modules/midi/build/default/midi.node
 → /tmp/remote-script/node_modules/midi/compiled/4.2.1/linux/mipsel/midi.node

There is a midi.node file at node_modules/midi/build/Release/midi.node. I’ve also tried running it with the --full flag, which fails with

node: '/tmp/remote-script/node_modules/midi/build/Release/midi.node' is not an ELF file

I’m on Node v5.9.1 and node-gyp v3.3.1 on OS X. Same error appears with Node v4.2.1.

Looks like someone had a similar issue with this package on a RaspberryPie.

Any insight into what’s causing this? I’m happy to defer this to the node-midi repo, just thought it might be handy to have here too. Thanks!

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 17 (10 by maintainers)

Most upvoted comments

Compiled and deployed:

  • midi@0.9.4

If you need a different version, we can re-open