Your message dated Sat, 12 Apr 2008 08:30:59 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#475618: xulrunner-dev-static: libxul.pc and
libxul-unstable.pc specify shared libraries outside /usr/lib, but no rpath
has caused the Debian Bug report #475618,
regarding xulrunner-dev-static: libxul.pc and libxul-unstable.pc specify shared
libraries outside /usr/lib, but no rpath
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.)
--
475618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475618
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xulrunner-dev-static
Version: 1.9~b4-1
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The library flags in libxul.pc and libxul-unstable.pc are:
- -L/usr/lib/xulrunner-devel-1.9/lib -lxpcomglue_s -lxul -lxpcom
libxul.so and libxpcom.so are installed in /usr/lib/xulrunner-1.9 so
these flags will result in executables that cannot be loaded unless
that directory is added to the library search using the -rpath linker
option or LD_LIBRARY_PATH.
However, if I understand correctly, libxpcomglue_s.a is supposed to
load libxul.so and libxpcom.so using dlopen() and executbales should
not refer to them at all. In that case, the .pc files should not
refer to these libraries at all.
Ben.
- -- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages xulrunner-dev-static depends on:
ii xulrunner-dev 1.9~b4-1 Development files for the Gecko en
xulrunner-dev-static recommends no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIAAT979ZNCRIGYgcRAjM1AJ9RcIOBa/64whUz/8yR9AQBUXt/gQCgzVzG
iKcP/yvqa3AF02LEn5GgS2s=
=P7+0
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Sat, Apr 12, 2008 at 01:40:29AM +0100, Ben Hutchings wrote:
> Package: xulrunner-dev-static
> Version: 1.9~b4-1
> Severity: normal
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The library flags in libxul.pc and libxul-unstable.pc are:
>
> - -L/usr/lib/xulrunner-devel-1.9/lib -lxpcomglue_s -lxul -lxpcom
>
> libxul.so and libxpcom.so are installed in /usr/lib/xulrunner-1.9 so
> these flags will result in executables that cannot be loaded unless
> that directory is added to the library search using the -rpath linker
> option or LD_LIBRARY_PATH.
I think it's not the .pc file role to enforce the use or rpath or
LD_LIBRARY_PATH.
> However, if I understand correctly, libxpcomglue_s.a is supposed to
> load libxul.so and libxpcom.so using dlopen() and executbales should
> not refer to them at all. In that case, the .pc files should not
> refer to these libraries at all.
This is the role of libxpcomglue, not libxpcomglue_s (yeah I know, names
could be better). libxpcomglue_s is what is called the dependant glue,
which means you then need to link against libxul and libxpcom.
This is not a bug ;)
Mike
--- End Message ---
