Re: *-config programs and multi-arch

[Tollef Fog Heen <tfheen@err.no>]

]] Miles Bader 

| Tollef Fog Heen <tfheen@err.no> 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 checked for using AC_PATH_TOOL, I
| > think and if you agree with that premise this should be fixed in
| > autoconf, not pkg-config.
| 
| Sure.  What's the best way to proceed then?  File a bug against
| autoconf?  [upstream?]

I'd assume so, upstream, yes.  Or mail the autoconf-devel list, I guess.

| [Someone mentioned that pkg-config also can be used for
| architecture-independent packages, but that seems like an orthogonal
| point, and not an overriding concern given than most packages aren't
| architecture-independent.]

Well, the cross-compiler-pkg-config will look in the arch-independent
directories too.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are