Sunday, May 1, 2011

so close on the computer end of things.

i am oh so close to getting the computer i want to run repsnapper up and running, but i seem to be missing something, i installed libreprap.so and when i was installing repsnapper it found it, but now when i run it i get this error message

repsnapper: error while loading shared libraries: libreprap.so: cannot open shared object file: No such file or directory

from what i can tell i have libreprap installed, but i have not been able to the this command to work for me

** cmake guis: cmake-curses-gui and cmake-qt-gui
but i am finding this one to be some what annoying i am also unsure how to do this or if this is the same error,

By default, the files are installed under /usr/local/, but some distros don't
include it into the search path for dynamic libs (running a binary that links
against libreprap might reports something like "Can't find libreprap.so" or so).
There are two ways to fix that:
* Change the install prefix to /usr/ instead of /usr/local, which is not recommended
* Add /usr/local/bin to ld.conf by creating a file /etc/ld.so.conf.d/local.conf which includes only the line "/usr/local/lib"
** run "sudo ldconfig" afterwards

if any one has some advice i would love it.
 
 
Posted by at
Your Reaction pleas: 

2 comments:

  1. I would suggest just changing the install prefix to /usr/, don't know why they recommend against it. In libreprap code directory:

    cmake -DCMAKE_INSTALL_PREFIX=/usr/ .

    then, like before:
    make && sudo make install

    Good luck!

    ReplyDelete

  2. LD_LIBRARY_PATH="/directory/that/libreprap.so/lives/in/" ./repsnapper

    I add LD_LIBRARY_PATH=~/lib to my .bashrc, then put my private libraries in ~/lib so this is basically done automatically for me.

    You could also add the path to /etc/ld.so.conf, or put librepsnapper.so in one of the paths in that file for a more permanent solution. Usually I leave that sort of thing to my package manager, but I haven't bothered writing an ebuild for libreprap yet

    ReplyDelete

Subscribe to: Post Comments (Atom)