On 22/09/2011 23:20, Steve Langasek wrote:
> On Thu, Sep 22, 2011 at 09:24:24AM +0200, Vincent Danjean wrote:
>> For my part, I think this is really error prone.
>
> Well, we'll have to agree to disagree then and let the maintainer decide.
Ok ;-)
>> Lots of native libraries will be wrongly detected as present when
>> cross-compiling.
>
> Why do you have -dev packages for "lots of native libraries" installed in
> your cross-build environment?
Because my cross-build environment is also my 'standard' environment.
I use my laptop to build lots of native software, but also to
cross-build arm and mips software (to be used by students).
> If you *have* a .pc for the foreign-arch library, why isn't this being found
> first (in one of the mentioned paths)?
It is. If it is present, it will always be found first.
> If you *don't* have a .pc for the foreign-arch library, you must not want to
> build against that library. Why doesn't the build system of the software
> you're building have an option to disable using that library even if
> present?
Generally, library are auto-detected by configure-like script. And, with
your proposal, the library will be (wrongly) found as present. With my
proposal, the library will be not found, leading either to desactivate
the part of the software using it or to generate an error (so that I can
install/cross-build this library and/or change configure options to not
use this library).
> I just don't see that being a common case; whereas I do see a big benefit to
> having this work out of the box with lots of -dev packages currently in the
> Debian archive, with no further modifications to pkg-config paths.
-dev packages are Arch: any, not Arch: all, aren't they? So, you need to
modify them using dpkg-cross ? Why cannot this tool move the .pc file to
the right location?
But perhaps, I do not see clearly your use case.
Regards,
Vincent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
