summaryrefslogtreecommitdiff
path: root/libxml-2.0.pc.in
diff options
context:
space:
mode:
authorArfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com>2012-08-28 22:16:50 +0800
committerDaniel Veillard <veillard@redhat.com>2012-08-28 22:16:50 +0800
commit1f01f49ba6abccc93a1779a05a33c3fb9c6efd4e (patch)
tree1817fd77aa06f127401acdf9cfbb85f2d9f5e596 /libxml-2.0.pc.in
parent961b535c10c7d07d7919c58c1d0c6762b35503a1 (diff)
downloadlibxml2-1f01f49ba6abccc93a1779a05a33c3fb9c6efd4e.tar.gz
Handle ICU_LIBS as LIBADD, not LDFLAGS to prevent linking errors
For https://bugzilla.gnome.org/show_bug.cgi?id=677606 For https://bugs.gentoo.org/show_bug.cgi?id=417539 If libxml2-2.8.0 is built with --with-icu --with-python on a system that has an older version of libxml2 installed, then during "make install", libxml2mod.so gets relinked to the systemwide version of libxml2.so.2 instead of libxml2.so.2 from the build tree, and fails at runtime if symbol versions from the older libxml2.so.2 are not available. This effectively makes it impossible to build a libxml2-2.8.0 binary package on a system that does not already have libxml2-2.8.0 installed. Investigation by Rafał Mużyło and Arfrever Frehtes Taifersar Arahesis revealed the cause of the problem to be that libxml2's configure was adding ICU_LIBS to LDFLAGS instead of to LIBADD. This resulted in GNU libtool using the wrong argument order in its relinking command that gets run during "make install".
Diffstat (limited to 'libxml-2.0.pc.in')
-rw-r--r--libxml-2.0.pc.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/libxml-2.0.pc.in b/libxml-2.0.pc.in
index 31a1b8ce..f5f5f03f 100644
--- a/libxml-2.0.pc.in
+++ b/libxml-2.0.pc.in
@@ -9,5 +9,5 @@ Version: @VERSION@
Description: libXML library version2.
Requires:
Libs: -L${libdir} -lxml2
-Libs.private: @THREAD_LIBS@ @Z_LIBS@ @ICONV_LIBS@ @M_LIBS@ @WIN32_EXTRA_LIBADD@ @LIBS@
+Libs.private: @ICU_LIBS@ @THREAD_LIBS@ @Z_LIBS@ @ICONV_LIBS@ @M_LIBS@ @WIN32_EXTRA_LIBADD@ @LIBS@
Cflags: @XML_INCLUDEDIR@ @XML_CFLAGS@