Paul Reinheimer wrote:
Thanks,
Through some carefull negotiations with the RPM i've managed to
upgrade to the requisite packages. ./configure was usefull along the
way, it raised errors letting me know what was missing.
Is the fact that ./configure didn't raise an error originally worth
filling out a bug report for? Am I likely to be able to provide enough
information for this to be looked at?
Your problem most likely stems from the fact that you are also building
with xsl. libxslt has a dependancy on libxml2 and when it picks up the
libxslt config (xslt-config), performed after the origional test for the
libxml2 library, it is pulling in the libxml2 it was built against (in
your case the old one). When installing a new version of libxml2 along
side an existing version rather than updating the existing version, you
need to build a new version of libxslt as well that links against the
new libxml2 and then use:
--with-libxml-dr=/path/to/new/libxml2
--with-xsl=/path/to/new/libxslt
Rob
