Unable to load shared library /Users/gabriel/app/node_modules/forever/node_modules/daemon/lib/daemon.v0.6.11.node

[gabipetrovay]

Hi,

I am using Node v0.6.11 on Mac OSX Lion.

I did npm rebuild and daemon.v0.6.11.node was rebuilt. (before it was daemon.v0.6.10.node).

When running forever module (that loads daemon module) I get:

node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: Unable to load shared library /Users/gabriel/Work/jillix/node_modules/forever/node_modules/daemon/lib/daemon.v0.6.11.node
    at Object..node (module.js:472:11)
    at Module.load (module.js:348:31)
    at Function._load (module.js:308:12)
    at Module.require (module.js:354:17)
    at require (module.js:370:17)
    at Object.<anonymous> (/Users/gabriel/app/node_modules/forever/node_modules/daemon/lib/daemon.js:12:11)
    at Module._compile (module.js:441:26)
    at Object..js (module.js:459:10)
    at Module.load (module.js:348:31)
    at Function._load (module.js:308:12)

otool says:

gabriel$ otool -L node_modules/forever/node_modules/daemon/lib/daemon.v0.6.11.node 
node_modules/forever/node_modules/daemon/lib/daemon.v0.6.11.node:
    /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

[indexzero]

Have you tried reinstalling it instead of rebuilding it?

[gabipetrovay]

Yes, both and it did not work. I HAD to rebuild otherwise you only have daemon.v0.6.10.node while daemon will look for the 0.6.11 version.

So I did both:

rm -R node_modules
npm install

or

npm rebuild

[gabipetrovay]

Any ideas on how this can be solved?

Thanks!

[TooTallNate]

@gabipetrovay Use the branch from my pull request using node-gyp in #12, and the proper version for your architecture will be built.

[gabipetrovay]

@TooTallNate Thank fit the tip! I would like to try the gyp branch. Do you know what the best way to try this is in an npm install scenario?

[indexzero]

This library is deprecated. Use detached child processes instead: http://nodejs.org/api/child_process.html#child_process_child_process_spawn_command_args_options