Bug#626579: libxpcom.so: cannot open shared object file: No such file or directory

Tim Rühsen tim.ruehsen at openmediasystem.de
Fri May 13 11:06:55 UTC 2011

Am Friday, 13. May 2011 schrieb Mike Hommey:
> On Fri, May 13, 2011 at 11:13:15AM +0200, Tim Rühsen wrote:
> > Sorry, I forget to say that it causes a problem with prelink:
> > prelink: /usr/lib/xulrunner-1.9.1/xulrunner-bin: Could not find one of
> > 
> >  the dependencies
> > 
> > This just means, this libraries would not prelink. Would be nice to avoid
> > such messages and have it going....
> Just set LD_LIBRARY_PATH when you prelink.
> Prelinking is a terrible idea anyway.

Prelinking is automatically done by cron when you install the package 
'prelink'. I don't like modifying the cron script since it is provided by the 
package as is.
What I did is putting a file into /etc/ld.so.conf.d/ which contains the 
library path '/usr/lib/xulrunner-1.9.1/'. But this a short time workaround 
which will break when xulrunner-1.9.1 is removed or replaced by a new version.

A proper solution still would be if xulrunner-x.y.z (whatever version) could 
provide the mentioned file. I have enough of these little things to keep in 
mind... computers are better at houskeeping library paths.
If you fix it, there are some nice side effects:
- prelink will work
- ldd will show the correct dependencies
- any program relying on ldd or prelink will work
( i am shure this list is not complete !)

> Prelinking is a terrible idea anyway.
It is beyond of the scope of this bug report... but maybe you could be more 
precise or link me to good discussions about pros and cons (never found a 
funded con that was relevant to me).
I personally use prelink since many years and can't remember any serious 
problems. But I just use on my desktop and not on any server. Just being 
precautious, not having a real reason.

Regards, Tim

More information about the pkg-mozilla-maintainers mailing list