Re: [PATCH] Use PKG_CHECK_MODULES to detect the libxml2 library
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hugh McMaster <hugh.mcmaster@outlook.com>
Cc: Daniel Gustafsson <daniel@yesql.se>,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-03-13T16:06:24Z
Lists: pgsql-hackers
Attachments
- 0001-pkg-check-modules-libxml2-v3.patch (text/x-diff) patch v3-0001
Hugh McMaster <hugh.mcmaster@outlook.com> writes: > On Fri, 13 Mar 2020 at 03:39, Tom Lane wrote: >> That won't win us any friends, so the attached revision >> doesn't call PKG_CHECK_MODULES unless we found pkg-config. > Did you mean to terminate configure if pkg-config cannot find > libxml-2.0 or the library is too old? Your doc changes don't indicate > that intent, nor was it prior behaviour, but some projects like that > behaviour and others don't. Yeah, a potential edge-case here is that pkg-config is in the PATH but it has no information about libxml2 (I doubt we need to consider the risk that it has info about a pre-2.6.23 version). Looking again at the generated configure code, I realize I shouldn't have left off the ACTION-IF-NOT-FOUND argument --- the default is to throw an error, but we'd rather fall through and try to use xml2-config. The eventual AC_CHECK_LIB(xml2, ...) test will catch the situation where the library isn't there. Updated patch attached. > You might consider this an edge case, but you override custom > XML2_CFLAGS/LIBS if xml2-config is detected. Yeah, if pkg-config fails and xml2-config is present, that's true. Since those weren't there before, and we now document them as just a fallback solution, I think that's fine. regards, tom lane
Commits
-
Use pkg-config, if available, to locate libxml2 during configure.
- d67d7243f914 10.13 landed
- 9af2f7dc9603 11.8 landed
- d8e7f8149400 12.3 landed
- 0bc8cebdb889 13.0 landed