On 3/4/13 1:36 PM, Noah Misch wrote:
Do you have in mind a target system exhibiting a problem? CentOS 6 ships a
single xml2-config, but its --cflags --libs output is the same regardless of
the installed combination of libxml2-dev packages. Ubuntu 13.04 does not ship
32-bit libxml2, so it
On Wed, Mar 20, 2013 at 05:17:11PM -0400, Peter Eisentraut wrote:
On 3/4/13 1:36 PM, Noah Misch wrote:
Do you have in mind a target system exhibiting a problem? CentOS 6 ships a
single xml2-config, but its --cflags --libs output is the same regardless of
the installed combination of
Noah Misch n...@leadboat.com writes:
On Wed, Mar 20, 2013 at 05:17:11PM -0400, Peter Eisentraut wrote:
On 3/4/13 1:36 PM, Noah Misch wrote:
Do you have in mind a target system exhibiting a problem? CentOS 6 ships a
single xml2-config, but its --cflags --libs output is the same regardless of
On Sun, Mar 03, 2013 at 10:30:11PM -0500, Peter Eisentraut wrote:
On Fri, 2013-03-01 at 14:25 -0500, Noah Misch wrote:
On Mon, Jan 14, 2013 at 06:51:05AM -0500, Peter Eisentraut wrote:
In multi-arch OS installations, using a single foo-config script to
find
libraries is problematic,
On Fri, 2013-03-01 at 14:25 -0500, Noah Misch wrote:
On Mon, Jan 14, 2013 at 06:51:05AM -0500, Peter Eisentraut wrote:
In multi-arch OS installations, using a single foo-config script to
find
libraries is problematic, because you don't know which architecture
it
will point to, and you
On Mon, Jan 14, 2013 at 06:51:05AM -0500, Peter Eisentraut wrote:
In multi-arch OS installations, using a single foo-config script to find
libraries is problematic, because you don't know which architecture it
will point to, and you can't choose which one you want. Using
pkg-config is better
On Mon, 2013-01-14 at 10:25 -0500, Tom Lane wrote:
Peter Eisentraut pete...@gmx.net writes:
The attached patch looks for pkg-config first, and finds libxml2 using
that if available. Otherwise it falls back to using xml2-config.
What happens if pkg-config is installed but doesn't know
In multi-arch OS installations, using a single foo-config script to find
libraries is problematic, because you don't know which architecture it
will point to, and you can't choose which one you want. Using
pkg-config is better in that situation, because you can use its
environment variables to
Peter Eisentraut pete...@gmx.net writes:
The attached patch looks for pkg-config first, and finds libxml2 using
that if available. Otherwise it falls back to using xml2-config.
What happens if pkg-config is installed but doesn't know anything about
xml2? I'd expect the code to fall back to
