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

Cannot find librhash.so.1 after installation with custom —prefix #239

Open
taprs opened this issue Jul 18, 2023 · 3 comments
Open

Cannot find librhash.so.1 after installation with custom —prefix #239

taprs opened this issue Jul 18, 2023 · 3 comments
Labels
as designed The code works as designed

Comments

@taprs
Copy link

taprs commented Jul 18, 2023

Hi and thanks for the tool!

I ran into error after running

./configure --prefix=${PWD} && make install

in the directory of the cloned repo. I cannot install into common directories due to access restrictions. As a result, the executable does not seem to detect the lib folder:

$ ./rhash
./rhash: error while loading shared libraries: librhash.so.1: cannot open shared object file: No such file or directory

Explicitly settint --libdir does not work too. Any ideas how to fix that?

@rhash
Copy link
Owner

rhash commented Jul 19, 2023

It looks that librhash got installed as librhash.so.1.4.4 without the symlink
librhash.so.1 -> librhash.so.1.4.4

On what OS did you encountered this bug?

@rhash
Copy link
Owner

rhash commented Jul 19, 2023

Ok, I now see that you are installing rhash into the current directory.

You should link the librhash statically into the rhash binary by command:

./configure --enable-static=librhash --prefix=${PWD} && make install

@rhash rhash added the as designed The code works as designed label Jul 19, 2023
@PraveenAlexis
Copy link

Hey, same thing happened to me.

I used ./configure && make install in Oracle Linux

I have a Prod and DEV envs, Prod is a clone of DEV fyi
However Rhash works in Dev and not in Prod

later I found out that, Rhash bin and the lib are in /usr/local/bin and /usr/local/lib respectively.
which is not detected by the OS

got it resolved by adding the paths to $PATH and $LD_LIBRARY_PATH

My question is why is that necessary? DEV env worked out of the box.

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

No branches or pull requests

3 participants