]] Miles Bader
| Tollef Fog Heen writes:
| > ]] Miles Bader
| > |When cross-compiling, there shouldn't be any default fallback for
| > |pkg-config if a cross-pkg-config (${ARCH}-pkg-config) isn't found;
| > |the current default behavior is more harmful than useful.
| >
| > You could
Tollef Fog Heen writes:
> ]] Miles Bader
> |When cross-compiling, there shouldn't be any default fallback for
> |pkg-config if a cross-pkg-config (${ARCH}-pkg-config) isn't found;
> |the current default behavior is more harmful than useful.
>
> You could argue this for any tool checke
]] Miles Bader
|When cross-compiling, there shouldn't be any default fallback for
|pkg-config if a cross-pkg-config (${ARCH}-pkg-config) isn't found;
|the current default behavior is more harmful than useful.
You could argue this for any tool checked for using AC_PATH_TOOL, I
think a
On 15/09/2011 20:56, Steve Langasek wrote:
> On Thu, Sep 15, 2011 at 01:37:55PM -0500, Peter Samuelson wrote:
>> It doesn't _look_ like it would work great:
>
>> PKG_CONFIG_LIBDIR=/usr/${triplet}/lib/pkgconfig pkg-config $@
>
>> Shouldn't that be /usr/lib/${triplet}/pkgconfig instead? I'd fi
]] Miles Bader
| I dunno, pkg-config is different, I think -- unlike a missing compiler
| or linker, a missing pkg-config often simply means "you can't use any
| libraries for which pkg-config is required", and missing libraries
| [etc] is an issue which configure scripts are often prepared.
You
Adam Borowski writes:
>> > AFAICT, the easiest way to handle all this is just to make a missing
>> > cross-pkg-config look like a missing pkg-config to the configure
>> > script. Then whatever logic the script may have for detecting the
>> > "not pkg-config at all" case, will do the right thing f
On Fri, 16 Sep 2011 11:06:05 +0200, Adam Borowski wrote:
Thus, please, could we get a $(TRIPLET)-pkg-config binary that does
know all
the magic needed? I insist on this name because this is what the
whole rest
of the toolchain does.
Just as well that's the name pkg-config upstream already ch
On Fri, Sep 16, 2011 at 02:38:50PM +0900, Miles Bader wrote:
> I earlier wrote:
> > AFAICT, the easiest way to handle all this is just to make a missing
> > cross-pkg-config look like a missing pkg-config to the configure
> > script. Then whatever logic the script may have for detecting the
> > "n
I earlier wrote:
> However, the current state, where it pretends pkg-config is present,
> when it really isn't in a useful way, just fools the configure script
> into doing the wrong thing.
>
> AFAICT, the easiest way to handle all this is just to make a missing
> cross-pkg-config look like a missi
On Thu, Sep 15, 2011 at 01:37:55PM -0500, Peter Samuelson wrote:
> > On Wed, Sep 14, 2011 at 10:42:07PM +0200, Tollef Fog Heen wrote:
> > > Your cross-toolchain is supposed to set up a symlink from
> > > /usr/bin/$triplet-pkg-config to /usr/share/pkg-config-crosswrapper which
> > > will then DTRT.
> On Wed, Sep 14, 2011 at 10:42:07PM +0200, Tollef Fog Heen wrote:
> > Your cross-toolchain is supposed to set up a symlink from
> > /usr/bin/$triplet-pkg-config to /usr/share/pkg-config-crosswrapper which
> > will then DTRT. That's the idea at least, I haven't actually tested
> > it.
[Steve Lan
On Thu, 15 Sep 2011 13:55:40 +0200
Bastien ROUCARIES wrote:
> On Thu, Sep 15, 2011 at 12:14 PM, Neil Williams wrote:
> > Please do not confuse cross-building (supplying the --host argument
> > to ./configure) with MultiArch (changing the paths in .install files
> > etc.) - the two impact on each
On Wed, Sep 14, 2011 at 03:01:06PM -0500, Peter Samuelson wrote:
> [Alastair McKinstry]
> > What is the preferred solution for handling these in the multi-arch
> > debian world? Currently I am working on providing pkg-config .pc
> > files as a replacement (and requesting that upstream deprecate t
On Wed, Sep 14, 2011 at 10:42:07PM +0200, Tollef Fog Heen wrote:
> ]] Peter Samuelson
> | I don't know how pkg-config handles multiarch either, but however
> | it detects the desired host arch (is it just the PKG_CONFIG_PATH
> | variable?), your /usr/bin/foo-config shouldn't have to care.
> Your
Simon McVittie writes:
> That's the missing piece of the puzzle: some sort of cross-toolchain
> package (which doesn't exist yet in Debian - but neither does a
> cross-gcc) should make the symlink
>
> x86_64-w64-mingw32-pkg-config -> /usr/share/pkg-config-crosswrapper
>
> in your $PATH. For th
Simon McVittie writes:
> That's the missing piece of the puzzle: some sort of cross-toolchain
> package (which doesn't exist yet in Debian - but neither does a
> cross-gcc) should make the symlink
>
> x86_64-w64-mingw32-pkg-config -> /usr/share/pkg-config-crosswrapper
>
> in your $PATH. For th
On Thu, Sep 15, 2011 at 12:14 PM, Neil Williams wrote:
> On Thu, 15 Sep 2011 10:33:52 +0200
> Bastien ROUCARIES wrote:
>
>> On Thu, Sep 15, 2011 at 9:53 AM, Miles Bader wrote:
>> > Tollef Fog Heen writes:
>> >> Your cross-toolchain is supposed to set up a symlink from
>> >> /usr/bin/$triplet-pk
On Thu, 15 Sep 2011 at 19:52:01 +0900, Miles Bader wrote:
> of course since there isn't an "x86_64-w64-mingw32-pkg-config"
> program, instead it just uses the normal pkg-config
That's the missing piece of the puzzle: some sort of cross-toolchain package
(which doesn't exist yet in Debian - but nei
Simon McVittie writes:
> On Thu, 15 Sep 2011 at 16:53:26 +0900, Miles Bader wrote:
>> Tollef Fog Heen writes:
>> > Your cross-toolchain is supposed to set up a symlink from
>> > /usr/bin/$triplet-pkg-config to /usr/share/pkg-config-crosswrapper which
>> > will then DTRT. That's the idea at least
On Thu, 15 Sep 2011 10:33:52 +0200
Bastien ROUCARIES wrote:
> On Thu, Sep 15, 2011 at 9:53 AM, Miles Bader wrote:
> > Tollef Fog Heen writes:
> >> Your cross-toolchain is supposed to set up a symlink from
> >> /usr/bin/$triplet-pkg-config to /usr/share/pkg-config-crosswrapper which
> >> will th
On Thu, 15 Sep 2011 at 16:53:26 +0900, Miles Bader wrote:
> Tollef Fog Heen writes:
> > Your cross-toolchain is supposed to set up a symlink from
> > /usr/bin/$triplet-pkg-config to /usr/share/pkg-config-crosswrapper which
> > will then DTRT. That's the idea at least, I haven't actually tested
>
Miles Bader writes:
> A brief browse of the pkg-config docs doesn't show any obvious
> user-level way of specifying an alternate host architecture. There's
> the environment variable "PKG_CONFIG_SYSROOT_DIR", but that seems a
> little low-level.
Also, PKG_CONFIG_SYSROOT_DIR doesn't really seem t
On Thu, Sep 15, 2011 at 9:53 AM, Miles Bader wrote:
> Tollef Fog Heen writes:
>> | I don't know how pkg-config handles multiarch either, but however
>> | it detects the desired host arch (is it just the PKG_CONFIG_PATH
>> | variable?), your /usr/bin/foo-config shouldn't have to care.
>>
>> Your c
Tollef Fog Heen writes:
> | I don't know how pkg-config handles multiarch either, but however
> | it detects the desired host arch (is it just the PKG_CONFIG_PATH
> | variable?), your /usr/bin/foo-config shouldn't have to care.
>
> Your cross-toolchain is supposed to set up a symlink from
> /usr/b
]] Peter Samuelson
| I don't know how pkg-config handles multiarch either, but however
| it detects the desired host arch (is it just the PKG_CONFIG_PATH
| variable?), your /usr/bin/foo-config shouldn't have to care.
Your cross-toolchain is supposed to set up a symlink from
/usr/bin/$triplet-pkg
[Alastair McKinstry]
> What is the preferred solution for handling these in the multi-arch
> debian world? Currently I am working on providing pkg-config .pc
> files as a replacement (and requesting that upstream deprecate the
> *-config scripts); I could rewrite the adios_config and dap-config
>
Hi,
In several packages I maintain there are programs that function like
pkg-config
(adios-config in adios; dap-config in libdap-dev). These then contain
architecture-specific
information similar to pkg-config files.
What is the preferred solution for handling these in the multi-arch
debian
27 matches
Mail list logo
