Linux Deployment Issues

[paixaop]

Linux Deployment Issues

[jamesbeecham]

Hi, I work with Dave.

We were able to get the library installed on the aws instance by yum install libsodium before npm install sodium. The drone.io build still fails.

James

[paixaop]

Have you tried installing a shared libsodium library on the system?

On 1/15/14, 2:39 AM, Dave Shapiro wrote:

Hi,

I am trying to run my application in two linux environments using
node-sodium.

On my local, mac, I have no problems building the libraries. But on my
continuous integration server (drone.io) and my staging env (amazon
aws [opsworks]) the app is failing. On drone i get the following error,

module.js:356
Module./extensionsextension <this,%20filename>;
^
Error: libsodium.so.4: cannot open shared object file: No such file or
directory
at Module.load (module.js:356:32)
at Function.Module./load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)

Has anyone experienced this/ know how to fix it?

Thank you ahead of time!

—
Reply to this email directly or view it on GitHub
#4.

[abenmrad]

Hi,

You seem to have fixed this issue in the current version on npm. I'm interested to know how you fixed it so I can do the same in my fork.

I know I can as well merge the changes from your repo, but I'm afraid it will break a lot of things I can't afford to fix right now.

I would really appreciate your help :)

[dsshap]

A compiled (on Amazon Linux) version of the library is here: https://github.com/ScoutAlarm/node-sodium-linux

I placed the file on the server (/usr/local/lib/node_modules) and reference its location for my nodejs app by setting the following env vars,

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$(pwd)/node_modules/sodium/libsodium/src/libsodium/.libs/
export LD_RUN_PATH=$LD_RUN_PATH:$(pwd)/node_modules/sodium/libsodium/src/libsodium/.libs/

[abenmrad]

@dsshap thanks for your reply, but since this is a cryptography library, I want to be able to compile it by myself, for obvious security reasons. :) If you can tell me how you fixed it, that'd be great. I don't see really the differences in the build process between your repo and mine

[dsshap]

@BatikhSouri follow the same approach that we did to successfully build it once in the environment you are going to use and then create a repo for that library, to avoid having to rebuild each time.

[abenmrad]

@dsshap Alright, your trick worked, thanks a lot :)