Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hard time building, not running on OS X #1

Closed
StevenLooman opened this issue Feb 6, 2012 · 3 comments
Closed

Hard time building, not running on OS X #1

StevenLooman opened this issue Feb 6, 2012 · 3 comments

Comments

@StevenLooman
Copy link

Great work! Unfortunately, it doesn't work on OS X (Lion)

After getting npm/mnm to use the correct library/include paths, it complains about being unable to find lib nnz11. nnz11 is NOT part of the Oracle InstantClient for OS X.

nnz10 is part of the Oracle InstantClient for OS X, however. After linking against that I get the following:

[Steven ~]$ node

require('oracle')
Segmentation fault: 11

Libraries oracle_bindings.node is linked against:

[Steven ~/node_modules/oracle/build/Release]$ otool -L oracle_bindings.node
oracle_bindings.node:
/opt/local/lib/oracle/libocci.dylib.10.1 (compatibility version 0.0.0, current version 0.0.0)
/opt/local/lib/oracle/libclntsh.dylib.10.1 (compatibility version 0.0.0, current version 0.0.0)
/opt/local/lib/oracle/libnnz10.dylib (compatibility version 0.0.0, current version 0.0.0)
/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)

@StevenLooman
Copy link
Author

Turns out sqlplus itself also gives a Segmentation fault: 11. Possible the Oracle InstantClient isn't Lion-compatible yet?

@joeferner
Copy link
Owner

Unfortunately this appears to be a problem with the 64-bit occi drivers on OSX (https://forums.oracle.com/forums/thread.jspa?threadID=2187558&tstart=0). The 32-bit drivers may work but node is compiled 64-bit so there is a mismatch.

@StevenLooman
Copy link
Author

I noticed. Was investigating a little further, but there indeed doesn't seem to be a fix. Migrated to NodeJS on Linux for now.

Thanks for the comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants