It's finally here, get your copy now! Node.js in Action - Amazon

Cross Compiling Node.js v0.8.x

Published: 2012.09.05

The #node.js IRC room has been getting a lot more requests for building Node.js for ARM processors lately. This has sparked my personal interest as well given the fact that I had to compile node for the Raspberry Pi in order for this blog to be running! That said, I'd like to share my experiences in cross-compiling from another computer.

Since building it on the Raspberry Pi itself takes over 2 hours (even though my device is overclocked by 150mhz), you really do want to learn how to cross-compile, especially if this is something you plan on doing often, which I do.

Getting prepared

This tutorial doesn't directly cover the setup of your cross-compiler. It is assumed you have that part figured out already. It will be necessary to have the gcc, g++, and ar programs from your cross-compiler working properly. In my case, these programs I will user are in my $PATH already with an "arm-unknown-linux-gnueabi" prefix:

  • arm-unknown-linux-gnueabi-gcc
  • arm-unknown-linux-gnueabi-g++
  • arm-unknown-linux-gnueabi-ar

Get the node source code

You can probably skip this step if you already have the node source code, but for reference, we need to clone the main repo and checkout the v0.8 branch:

$ git clone git://
$ cd node
$ git checkout v0.8

You may checkout a stable tag like v0.8.8 if you'd like instead. It's up to you.

Optional: I also have a pi branch that's based off of the v0.8 branch, which includes an upstream libuv patch to fix os.cpus() on ARM processors, and an upstream V8 fix to work properly on ARM processors that only inclue support for VFP2, but not VFP3. You can check that out here if you'd like:

Update: My pi branch has been merged upstream into node, so v0.8.10 and newer should "just work" on Raspberry Pi and many other ARM platforms.

Set "exports"

Cross-compiling with gyp is actually not so bad. It turns out we only need to set 4 env variables and things seems to works as expected after:

$ export AR=arm-unknown-linux-gnueabi-ar
$ export CC=arm-unknown-linux-gnueabi-gcc
$ export CXX=arm-unknown-linux-gnueabi-g++
$ export LINK=arm-unknown-linux-gnueabi-g++

Note that the LINK variable points to your g++ program rather than your ld program, since the Makefile uses some flags that ld does not recognize.

The "configure" step

At this point we can execute the ./configure step. The only catch here is that we have to disable V8 "snapshot" support, since it requires being able to run the compiled code natively, which is not possible when cross-compiling.

$ ./configure --without-snapshot --dest-cpu=arm --dest-os=linux

The --dest-os flag is only available in v0.8.9 of node and newer (or just use my "pi" branch mentioned above).

The "make" step

And now it's time to run make. This is the whole reason we're cross-compiling: to cut this step down, in my case, from 2 hours to 2 minutes. In fact, since I'm going to be cross-compiling on a quad-core machine with hyper threading, I'll go ahead and utilize Make's --jobs switch to parallelize the build. I'm going to use a value of 8 but you should set that to roughly the number of CPU cores you have.

$ make --jobs=8

We're done!

If things went well, you should have a shiny new node executable for your target architecture. We can verify that with the file command:

$ file out/Release/node
out/Release/node: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.1.10, not stripped

file says "ARM" and "for GNU/Linux" so we're looking good. Go ahead and transfer that file to your target machine and try things out! Let me know in the comments if things work out for you or not.