More details: https://github.com/brianmcd/contextify/issues/19
Seems like a strange problem ...
When I updated from v0.6.10 to 0.6.11 the date of the installed node-waf is older but the files appear identical.
$ node --version
v0.6.10
$ ls -l /usr/local/bin/node-waf
-rwxr-xr-x 1 24561 wheel 355 Feb 2 19:56 /usr/local/bin/node-waf
$ ls -l /usr/local/bin/node
-rwxr-xr-x 1 24561 wheel 6683464 Feb 2 19:59 /usr/local/bin/node
$ node --version
v0.6.11
$ ls -l /usr/local/bin/node-waf
-rwxr-xr-x 1 24561 wheel 355 Jan 19 20:53 /usr/local/bin/node-waf
$ ls -l /usr/local/bin/node
-rwxr-xr-x 1 24561 wheel 6021212 Feb 17 15:54 /usr/local/bin/node
What architectures are node and your add-on compiled for? Run `file
/usr/local/bin/node` and `file /path/to/contextify.node` and compare
the results.
Ahh ... v0.6.10 is a 64-bit executable:
$ node --version
v0.6.10
$ file `which node`
/usr/local/bin/node: Mach-O 64-bit executable x86_64
But installing the latest version of node from the pkg hosted here results in a 32-bit executable:
http://nodejs.org/dist/v0.6.11/node-v0.6.11.pkg
$ node --version
v0.6.11
$ file `which node`
/usr/local/bin/node: Mach-O executable i386
This seems to be a mistake in the building/packaging of node-v0.6.11.pkg
In either case contextify builds a 64-bit shared library.