Re: Re: Introduction to multiarch: What maintainers must do

[Gabor Gombas <gombasg@sztaki.hu>]

On Thu, Jul 30, 2009 at 11:04:46AM +0200, Samuel Thibault wrote:

> > >Yes, but however pkg-config won't yet find things in
> > >/usr/lib/x86_64-linux-gnu/pkgconfig, so take care of putting .pc files
> > >in /usr/lib/pkgconfig.

$ pkg-config --list-all --debug
[...]
Cannot open directory '/usr/local/lib/pkgconfig' in package search path: No such file or directory
Cannot open directory '/usr/local/lib/pkgconfig/x86_64-linux-gnu' in package search path: No such file or directory
Scanning directory '/usr/lib/pkgconfig'
[...]
Cannot open directory '/usr/lib/pkgconfig/x86_64-linux-gnu' in package search path: No such file or directory
[...]

So pkg-config already has some support for multi-arch, it just uses
different directories than the current proposal. That can be fixed with
either a single symlink, or by modifying the --with-pc-pass=... argument
in pkgconfig's debian/rules. Neither will allow building stuff for a
different architecture, but as you note below that's not a requirement
for now.

Later pkg-config should be extended to have an "--arch" command-line
option (or env. variable) that is substituted into the default search
path at run time rather than at build time, but that can wait.

> > Please don't as those files can be different on different  
> > architectures.
> 
> Yes, but for now multi-arch support for -dev packages won't be done so
> it's not a problem.

But if it can be fixed with a simple change to pkg-config, then why not
move the .pc files now? Esp. if that means less work for the library
package maintainers.

Gabor

-- 
     ---------------------------------------------------------
     MTA SZTAKI Computer and Automation Research Institute
                Hungarian Academy of Sciences
     ---------------------------------------------------------