cainus/Prozess

Example code fails to start.

Closed this issue · 3 comments

BorePlusPlus commented

I am evaluating node.js kafka libraries. While running the Prozess example code (both producer and consumer are affected) I get the following error:
module.js:485
process.dlopen(filename, module.exports);
^
Error: dlopen(/Users/bore/projects/node-playground/node_modules/Prozess/node_modules/buffermaker/node_modules/bignum/build/Release/bignum.node, 1): no suitable image found. Did find:
/Users/bore/projects/node-playground/node_modules/Prozess/node_modules/buffermaker/node_modules/bignum/build/Release/bignum.node: mach-o, but wrong architecture
at Object.Module._extensions..node (module.js:485:11)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:362:17)
at new require (module.js:378:17)
at Object. (/Users/bore/projects/node-playground/node_modules/Prozess/node_modules/buffermaker/node_modules/bignum/index.js:6:14)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)

From reading the stack trace it seems it might be an issue with an underlying library (bignum), but I am too fresh to node to be sure.

I am running node.js v0.8.20 on a mac.

Thanks

Sedward commented

Hello. The problem is indeed the bignum library. How did you install Node.js? We've also found the error and we opened an issue on the bignum project. We've found that the error does NOT occur if we build Node from source.

Here is the open issue on bignum justmoon/node-bignum#11

BorePlusPlus commented

Hi. Thanks for prompt reply. I am indeed using node.js installed via installer. I guess I'll give it a shot with the compiled one (as soon as I figure out how to get rid of the installer one).

Cheers

elee commented

Two more closing thoughts:

  1. Perhaps there's a more explicit way to check our supported node version is being invoked at npm install time and emit a pre-emptive install error. Documenting supported versions of node could help too.
  2. You could try using 'n' to switch your working version of node and try again. n is the node.js analogue to rvm in Ruby, virtualenv in Python etc.