Your message dated Tue, 18 Oct 2011 07:35:56 +0200
with message-id <[email protected]>
and subject line Re: Bug#645706: xulrunner-7.0: Please make a libmozalloc,
libxpcom, libxul known to ldconfig
has caused the Debian Bug report #645706,
regarding xulrunner-7.0: Please make a libmozalloc, libxpcom, libxul known to
ldconfig
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
645706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645706
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xulrunner-7.0
Version: 7.0.1-4
Severity: minor
Hi,
I have an FF extension that its so file is dependent of libmozalloc.so,
libxpcom.so and libxul.so which are supplied by xulrunner-7.0.
running ldd over the file shows there libraries as 'not found'. This seems
to be due to the fact that there isn't any symlink in a location that
ldconfig could get to know these shared objects.
I've worked around the problem with these symlinks:
desktop:~# ln -s /usr/lib/xulrunner-7.0/libxpcom.so /usr/lib/libxpcom.so
desktop:~# ln -s /usr/lib/xulrunner-7.0/libxul.so /usr/lib/libxul.so
desktop:~# ln -s /usr/lib/xulrunner-7.0/libmozalloc.so
/usr/lib/libmozalloc.so
Thanks,
Kaplan
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xulrunner-7.0 depends on:
ii libasound2 1.0.24.1-4
ii libatk1.0-0 2.2.0-2
ii libbz2-1.0 1.0.5-7
ii libc6 2.13-21
ii libcairo2 1.10.2-6.1
ii libdbus-1-3 1.4.16-1
ii libevent-1.4-2 1.4.14b-stable-1
ii libfontconfig1 2.8.0-3
ii libfreetype6 2.4.6-2
ii libgcc1 1:4.6.1-15
ii libgdk-pixbuf2.0-0 2.24.0-1
ii libglib2.0-0 2.28.8-1
ii libgtk2.0-0 2.24.6-2
ii libhunspell-1.3-0 1.3.2-4
ii libjpeg8 8c-2
ii libmozjs7d 7.0.1-4
ii libnotify4 0.7.4-1
ii libnspr4-0d 4.8.9-1
ii libnss3-1d 3.12.11-3
ii libpango1.0-0 1.29.4-1
ii libpixman-1-0 0.22.2-1
ii libreadline6 6.2-7
ii libsqlite3-0 3.7.8-1
ii libstartup-notification0 0.12-1
ii libstdc++6 4.6.1-15
ii libvpx0 0.9.7.p1-2
ii libx11-6 2:1.4.4-2
ii libxext6 2:1.3.0-3
ii libxrender1 1:0.9.6-2
ii libxt6 1:1.1.1-2
ii zlib1g 1:1.2.3.4.dfsg-3
xulrunner-7.0 recommends no packages.
Versions of packages xulrunner-7.0 suggests:
ii libcanberra0 0.28-2
ii libdbus-glib-1-2 0.98-1
ii libgnomeui-0 2.24.5-2
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Oct 18, 2011 at 12:58:50AM +0200, Lior Kaplan wrote:
> Package: xulrunner-7.0
> Version: 7.0.1-4
> Severity: minor
>
> Hi,
>
> I have an FF extension that its so file is dependent of libmozalloc.so,
> libxpcom.so and libxul.so which are supplied by xulrunner-7.0.
>
> running ldd over the file shows there libraries as 'not found'. This seems
> to be due to the fact that there isn't any symlink in a location that
> ldconfig could get to know these shared objects.
>
> I've worked around the problem with these symlinks:
> desktop:~# ln -s /usr/lib/xulrunner-7.0/libxpcom.so /usr/lib/libxpcom.so
> desktop:~# ln -s /usr/lib/xulrunner-7.0/libxul.so /usr/lib/libxul.so
> desktop:~# ln -s /usr/lib/xulrunner-7.0/libmozalloc.so
> /usr/lib/libmozalloc.so
If it's an extension, it will be loaded by xulrunner. If it is loaded by
xulrunner, the libraries will be found.
Cheers,
Mike
--- End Message ---
