-
Notifications
You must be signed in to change notification settings - Fork 356
Run with older libc #132
Comments
You could try to compile lmdbjni. We use the library from https://github.com/deephacks/lmdbjni It is specified in the following lines: After you build your own lmdbjni, you need to change the above pom.xml accordingly so that it does not fetch from maven repo. You may need to change the top level make file concerning the location of liblmdbjni.so, as well. |
I don't have experience with maven. Could you please elaborate on what I need to do to use a custom liblmdbjni.so? Edit: I now have a locally compiled copy of
How do I update the pom.xml to use a locally built version of this library? |
I managed to get past this issue by using the instructions here to install the locally built liblmdbjni to the maven local repo. This was version Please note that simply replacing the .so after the build does not do the same for some reason. Edit: At some point I also tried |
To add you local files to maven build, you can use maven system dependency or install them into your local maven repo. http://stackoverflow.com/questions/4955635/how-to-add-local-jar-files-in-maven-project |
I am trying to run this on a cluster that has libc version 2.12 and on trying to run the mnist example I get the following error:
Clearly,
liblmdbjni.so
was compiled with a higher version of libc. On checking the build logs, I realise that this library was never compiled as part of the build and was actually distributed as a binary.My choices now are:
Option 2 above becomes harder since I don't have root access to the cluster so
chroot
isn't an option. The path told
is hardcoded inside the binary and will always be searched inside/lib
.Any ideas here?
The text was updated successfully, but these errors were encountered: