On Fri, 02 Dec 2005, Ian Jackson wrote:
> > Indeed, rpath is only acceptable for:
> > 1. dynamically loaded modules/plugins
> > 2. libraries that must live outside of ld.so directories
>
> And these things might reasonably be searched for in
> /usr/local/lib/foo as well as /usr/lib/foo.
rpath
Henrique de Moraes Holschuh writes ("Re: [Proposal] binaries must not have
rpath outside /usr/lib//"):
> On Wed, 30 Nov 2005, Ian Jackson wrote:
> > Just as one example, a program might reasonably have an rpath in
> > /usr/local/lib//. [...]
>
> Not in Debian, it doesn't. Since policy is about
Henrique de Moraes Holschuh writes ("Re: [Proposal] binaries must not have
rpath outside /usr/lib//"):
> On Fri, 02 Dec 2005, Ian Jackson wrote:
> > > Indeed, rpath is only acceptable for:
> > > 1. dynamically loaded modules/plugins
> > > 2. libraries that must live outside of ld.so directorie
On Fri, 02 Dec 2005, Ian Jackson wrote:
> A sensible way to arrange for this to work might be for
> /usr/bin/frobnicate's rpath to specify /usr/lib/frobnicate/modules.
> That way frobnicate can load `frictive' without having to specify the
> path.
Hmm... (reads ELF 1.2). Oh drat, DT_RPATH is a col
Processing commands for [EMAIL PROTECTED]:
> submitter 205956 !
Bug#205956: xml-resume-library: Wrong name for jar file
Changed Bug submitter from Cesar Eduardo Barros <[EMAIL PROTECTED]> to Cesar
Eduardo Barros <[EMAIL PROTECTED]>.
> submitter 24239 !
Bug#24239: xbase-clients: [xsm] fails to re
5 matches
Mail list logo