cuneiform does not find its librarie libpuma.so

Bug #345033 reported by Koose
4
Affects Status Importance Assigned to Milestone
Cuneiform for Linux
Invalid
Undecided
Yury V. Zaytsev

Bug Description

Hi!

After installing cuneiform, I tried to start it the first time. But the output is:

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

I found libpuma.so at /usr/local/lib, but cuneiform does not.

Can anyone help?

Thanks
Koose

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

Add /usr/local/lib to /etc/ld.so.conf and run ldconfig. Seems like that you have a misconfigured system which does not pick up libs from /usr/local atomagically.

Revision history for this message
Koose (koose) wrote :

That worked. Thanks.

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

Closing as invalid (not a bug).

Changed in cuneiform-linux:
assignee: nobody → zyv
status: New → Invalid
Revision history for this message
Leonid Selivanov (bravebug-deactivatedaccount) wrote :

I encountered the same problem. But I have Ubuntu 9.04 x86_64 and I fined libpuma.so in /usr/local/lib64/
I helped only: 'ln -s /usr/local/lib64/*.so /usr/lib64/' from root, because it need all this *.so

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

Then go fill a bug against Ubuntu, a sane system should pick up the libraries in /usr/local/lib* automatically. Ubuntu Hardy does this, no idea why they dropped it into subsequent releases.

Revision history for this message
Martin Wildam (mwildam) wrote :

FYI: For me under Jaunty it was sufficient to rerun ldconfig as the configuration in /etc/ld.so.conf.d looked ok. So it seems that when the configuration got updated the ldconfig was not rerun.

Revision history for this message
Vermenko Yuriy (vyv) wrote :

Как вариант можно сделать символьные ссылки в директории /usr/lib

Revision history for this message
julien (julien-aubert) wrote : RE: [Cuneiform] [Bug 345033] Re: cuneiform does not find its librarie libpuma.so

Which version did you download?
Have you installed previous versions?

Which commands did you run to install?
Did you use any prefix option or similar when compiling?

Julien
________________________________________
Från: <email address hidden> [<email address hidden>] f&#246;r Vermenko Yuriy [<email address hidden>]
Skickat: den 4 oktober 2009 23:46
Till: <email address hidden>
Ämne: [Cuneiform] [Bug 345033] Re: cuneiform does not find its librarie libpuma.so

Как вариант можно сделать символьные ссылки в директории /usr/lib

--
cuneiform does not find its librarie libpuma.so
https://bugs.launchpad.net/bugs/345033
You received this bug notification because you are a member of Cuneiform
Linux, which is the registrant for Cuneiform for Linux.

Status in Linux port of Cuneiform: Invalid

Bug description:
Hi!

After installing cuneiform, I tried to start it the first time. But the output is:

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

I found libpuma.so at /usr/local/lib, but cuneiform does not.

Can anyone help?

Thanks
Koose

_______________________________________________
Mailing list: https://launchpad.net/~cuneiform
Post to : <email address hidden>
Unsubscribe : https://launchpad.net/~cuneiform
More help : https://help.launchpad.net/ListHelp

Revision history for this message
Martin Wildam (mwildam) wrote :

In my case (not the OP) I used the latest (v0.8.0).

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

Great, thanks for the info! This implies that we will only need to do ldconfig after the installation of the package (when we're going to look into packaging at last, I mean).

Revision history for this message
Martin Wildam (mwildam) wrote :

At least for Jaunty, I mean. ;-) - We will see what will be needed on Karmic...

Revision history for this message
Jussi Pakkanen (jpakkane) wrote :

For packaging you might want to look how Debian does it with RPATH.

http://packages.qa.debian.org/c/cuneiform.html

Revision history for this message
adriverhoef (a3) wrote :

If you run into this error and don't like editing your system files, you could try adding the environment variable "LD_LIBRARY_PATH" to your shell before calling 'cuneiform' e.g. by adding the following line to your .bash_profile:
export LD_LIBRARY_PATH=/usr/local/lib

... or you could create a script that calls the real 'cuneiform' e.g. like this:
   LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/cuneiform "$@"

Here's a sample script that I use for a specific job that converts PNM-files:

#!/bin/sh
for pnm in *.pnm
do
 [ -f "$pnm" ] || break
 printf "Processing %s ...\n" "$pnm"
 ppmtobmp "$pnm" > "${pnm%%.pnm}.bmp"
 LD_LIBRARY_PATH=/usr/local/lib cuneiform -l eng -f smarttext -o ${pnm%%.pnm}.eng ${pnm%%.pnm}.bmp
done

Revision history for this message
Alexander Dolgunin (a-dolgunin) wrote :

I confirm that on Ubuntu Hardy I had to run ldconfig after installation.
Should this be mentioned in readme, incorporated into Makefile or is it Ubuntu's fault?

On Debian Lenny AMD64 I had PUMA_Init failed. Fresh install of Cuneiform in both cases, with just
mkdir builddir
cd builddir
cmake ..
make
sudo make install

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

Yes, it should be mentioned in the README.

Revision history for this message
Jussi Pakkanen (jpakkane) wrote :

The fact that Ubuntu does not have /usr/local/lib in linker path is their choice (some would call it a bug). Any self-built program with shared libraries will behave exactly the same.

Revision history for this message
Yury V. Zaytsev (zyv) wrote :

Jussi, it does, at least for Hardy. But even if the library is in the linker path you have to run ldconfig before you can actually use it. Not only on Ubuntu, but also RHEL/Fedora and any other systems where the libraries are managed by ldconfig.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.