Bug 184170 - xml2-config lies
Summary: xml2-config lies
Alias: None
Product: Fedora
Classification: Fedora
Component: libxml2 (Show other bugs)
(Show other bugs)
Version: 4
Hardware: i386 Linux
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-03-06 23:20 UTC by Ben Allan
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-07 08:46:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ben Allan 2006-03-06 23:20:00 UTC
Description of problem:
As someone has chosen not to install libxml2.la with the package or the devel
package, xml2-config --libtool-libs should report the empty string or better
yet a detectable error message; this is an egregious error, but
if at least properly handled by modifying xml2-config, other
packages expecting libxml2.la at configure time can compensate reliably.
libxml2.la is installed by default if
building and installing from xmlsoft.org downloaded sources.

Version-Release number of selected component (if applicable):

How reproducible:
x=`xml2-config --libtool-libs`
ls -l $x

Actual results:
ls: /usr/lib/libxml2.la: No such file or directory

Expected results:
xml2-config: error: libtool archives not packaged for fedora. blame the packager.

Additional info:

Comment 1 Daniel Veillard 2006-03-07 08:46:06 UTC
libtool archives are not not packaged in Fedora/RHEL as a policy for all
libraries. Blaming the packager who is also the person bringing you the
hundred of thousand of lines of code of this library is of really poor
taste, blame is too easy on the receiving end. 
Try to pick less insulting terms (lie, blame ...) next time you ask for
something, thanks in advance.

That said I mofified it upstream to not report a value if the file is not


Note You need to log in before you can comment on or make changes to this bug.