On Fri, Jul 01, 2011 at 09:28:24AM -0700, Ian Wienand wrote:
> Hi,
>
> Thanks, I realised this after I sent it
>
> I'm not sure though if it's multi-arch or elfutils? The man page says
>
> $LIB The string $LIB (or equivalently ${LIB}) in an rpath corresponds
> to the system libraries directory, which is /lib for the native
> architecture on FHS compliant GNU/Linux systems.
>
> But "system libraries directory" is a bit vague w.r.t multi-arch :)
> Are you supposed to do $ORIGIN../lib/$LIB now? And I guess the .so's
> need be shipped there too
It sets up an rpath, and the manpage says:
$ORIGIN
ld.so understands the string $ORIGIN (or equivalently ${ORIGIN})
in an rpath specification to mean the directory containing the
application executable. Thus, an application located in
somedir/app could be compiled with gcc -Wl,-rpath,'$ORI-
GIN/../lib' so that it finds an associated shared library in
somedir/lib no matter where somedir is located in the directory
hierarchy.
I have no idea why something is trying to open it in
i386-linux-gnu, it clearly seems wrong to me.
So I think I'm going to reassign this to eglibc.
Kurt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
