Johnny-five: Bindings don't work on Raspberry Pi

[beriberikix]

I'm trying to get Johnny Five running on Raspbian. NPM was having issues (and the native extensions wouldn't compile) but the bindings are erroring out. Is that on the Firmata side of things?

/home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/node_modules/bindings/bindings.js:85
throw err
^
Error: Could not load the bindings file. Tried:
-> /home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/build/Debug/serialport.node
-> /home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/build/Release/serialport.node
-> /home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/out/Debug/serialport.node
-> /home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/Debug/serialport.node
-> /home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/out/Release/serialport.node
-> /home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/Release/serialport.node
-> /home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/build/default/serialport.node
-> /home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/compiled/0.6/linux/arm/serialport.node
at bindings (/home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/node_modules/bindings/bindings.js:82:13)
at Object. (/home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/node_modules/serialport/serialport.js:7:44)
at Module._compile (module.js:446:26)
at Object..js (module.js:464:10)
at Module.load (module.js:353:32)
at Function._load (module.js:311:12)
at Module.require (module.js:359:17)
at require (module.js:375:17)
at Object. (/home/pi/www/j5/node_modules/johnny-five/node_modules/firmata/lib/firmata.js:9:18)
at Module._compile (module.js:446:26)

[rwaldron]

Unfortunately, this is first documented failure on Rasberry PI, previous attempts were all successful. The issue is with compiling the serialport bindings - so it should be filed with node-serialport. However, it seems that the issue is usually fixed by installing node-gyp globally (IIRC)

[beriberikix]

No dice. npm install -g node-gyp and same thing. I'm going to take a deeper
look at my node build or Raspberian itself to see if there's anything there.

I'll follow up with serialport and post the results here - but you can
close for now.

On Wed, Aug 15, 2012 at 3:38 PM, Rick Waldron [email protected]:

Unfortunately, this is first documented failure on Rasberry PI, previous
attempts were all successful. The issue is with compiling the serialport
bindings - so it should be filed with node-serialport. However, it seems
that the issue is usually fixed by installing node-gyp globally (IIRC)

—
Reply to this email directly or view it on GitHubhttps://github.com/rwldrn/johnny-five/issues/58#issuecomment-7771709.

[rwaldron]

Let's get @paultag in on this

[paultag]

On it, give me a few.

[rwaldron]

Awesome. @beriberikix this is @paultag, he's a debian committer and raspberry pi owner as well, and so hopefully he can help get up and running :)

[paultag]

@beriberikix My IO is gnarly (SD card problems), but serialport is installing via npm correctly -- I'm going to look into this s'more, but can you pastebin the full output / npm debug log while I wait for this guy to finish crunching?

[paultag]

Eeek, issue ACK'd. Let me see here. I think I saw something in the backspew.

[beriberikix]

Thanks @paultag! I'll stay posted.

[paultag]

OK, @beriberikix, got this going.

Two things that suck:

• So, node-gyp does need to be globally installed (I can't endorse doing this via npm, but if it works, I guess it works ;) )
• npm is not (fully?) running the binding.gyp in serialport (le sigh) -- the fix was simple on my end, cd into the node_modules/serialport and issue a quick node-gyp configure and a nice solid node-gyp build. Keep in mind you'll need a basic toolchain (etc), which can be provided with build-essential (at least).

You can verify it looks sane by cd'ing into node_modules/serialport and running this snippit:

if [ "x`find . -name "serial*node"`" = "x" ]; then echo "Something sucks"; else echo "Looks OK"; fi

Happy hacking!

If this fixes this, feel free to close the bug, or re-assign to serialport :)

[beriberikix]

w00t! I'm cooking with jet fuel! Thanks @paultag & @rwldrn.

[paultag]

You got it, rock on!