Raphael Hertzog wrote:
> On Wed, 28 Nov 2007, Neil Williams wrote:
>> I thought Guillem wanted to review the use of /usr/arm-linux-gnu/lib and
>> /usr/arm-linux-gnu/include ? I do have perl code that solves the problem
>> (used it to cross build GPE for Emdebian) involving adding search
>> directories to LD_LIBRARY_PATH but I wasn't sure if Guillem was looking
>> at a different implementation for those directories.
> 
> I don't know what he plan to do, but for dpkg-shlibdeps's part it's clear
> that we need to fix the list of directories to search. So I'd be ready to
> apply a patch for this part. We can always tweak it later if needed.

OK.

>> CC'ing debian-dpkg to find out.
> 
> Guillem gets the BTS mail, no need for an explicit CC to the list.

Oops. Sorry.

>> directory of symlinks or something else? Should Raphael and I work on a
>> solution for dpkg-shlibdeps using LD_LIBRARY_PATH using the example below?
> 
> The real fix doesn't change LD_LIBRARY_PATH but directly the official list of
> directories in scripts/Dpkg/Shlibs.pm and also directories listed in
> a LD_LIBRARY_PATH submitted by the package might need to be adjusted
> in a similar way (s|/usr/lib/|/usr/<arch-triplet>/lib/|) (provided that
> the on-the-fly conversion done by dpkg-cross converts all of what's below
> /usr/lib/ in packages in that way.

Yes, that sounds good - the only reason I change LD_LIBRARY_PATH right
now is because dpkg-shlibdeps reads that variable. If the change is done
within it, then I agree, we shouldn't need to touch LD_LIBRARY_PATH
directly.

>> That is what I'm using with the current dpkg-shlibdeps from 1.14.11 and
>> AFAICT it is fine (providing that the cross paths are added to the
>> standard paths and not replace them or perl gets confused).
> 
> Care to elaborate on why perl gets confused ? 

If LD_LIBRARY_PATH does not include /usr/lib/ but only
/usr/$triplet/lib, perl cannot find it's own shared objects (presumably
within the interpreter).

This only became noticeable when I tried to set LD_LIBRARY_PATH in a
perl script that then called another perl script - the system call
failed and perl complained about a broken installation.

> In any case, since we would _not_ change LD_LIBRARY_PATH, it shouldn't be
> a problem.

Agreed.

I'll see about a patch later today.

It's the effect of the change that I need, not the current method.

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to