c++ BSON extension error. Can't find errors in build..?

[Jared]

This is the error I'm getting on starting up my node.js app (Node.js v 0.12.0):

[Error: .../node_modules/mongodb/node_modules/bson/build/Release/bson.node: undefined symbol: node_module_register]
js-bson: Failed to load c++ bson extension, using pure JS version


I did what I could looking at what was posted here: http://christiankvalheim.com/post/diagnose_installation_problems/

The js-bson test is giving me this result at the bottom:
OK: 55963 assertions (649ms)

I assume that means that the test works fine.

After that, I ran npm --loglevel verbose install mongodb

I didn't see anything that *looked* alarming or incorrect except a couple of lines like this interspersed in the readout:

> bs...@0.2.19 install /home/e6serv/e6Code/e6Inner/node_modules/mongodb/node_modules/bson
> (node-gyp rebuild 2> builderror.log) || (exit 0)
make: Entering directory `/home/e6serv/e6Code/e6Inner/node_modules/mongodb/node_modules/bson/build'
  g++ '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DBUILDING_NODE_EXTENSION' -I/home/jared/.node-gyp/0.12.0/src -I/home/jared/.node-gyp/0.12.0/deps/uv/include -I/home/jared/.node-gyp/0.12.0/deps/v8/include -I../node_modules/nan  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -ffunction-sections -fdata-sections -fno-tree-vrp -fno-tree-sink -fno-omit-frame-pointer -fno-rtti -MMD -MF ./Release/.deps/Release/obj.target/bson/ext/bson.o.d.raw  -c -o Release/obj.target/bson/ext/bson.o ../ext/bson.cc
  flock ./Release/linker.lock g++ -shared -pthread -rdynamic -m64  -Wl,-soname=bson.node -o Release/obj.target/bson.node -Wl,--start-group Release/obj.target/bson/ext/bson.o -Wl,--end-group
  SOLINK_MODULE(target) Release/obj.target/bson.node: Finished
  rm -rf "Release/bson.node" && cp -af "Release/obj.target/bson.node" "Release/bson.node"
make: Leaving directory `/home/e6serv/e6Code/e6Inner/node_modules/mongodb/node_modules/bson/build'


Another thread on this forum led me to believe that's not an issue, simply informational. I got no errors that I could see (though the log is truncated a few screens up by my terminal.)

What now? Can anybody tell me what I should be doing about this? (It's not an immediate problem but I don't like having to rely on the pure JS version when the c++ is available)

[Эдгар Маркосов]

воскресенье, 15 марта 2015 г., 8:20:20 UTC+4 пользователь Jared написал:

I have the same problem with node 0.12.0, but with versions 0.10.x (mine is 0.10.33) it works without this warning. Can anyone provide the solution ? And I have noticed that with node 0.12.0 the 'npm install mongodb' command  does not finish, with node 0.10.33, for instance, it finishes properly.