libxslt port build problem

[Kevin Oberman]

> Date: Mon, 09 Nov 2009 09:15:52 +0000
> From: Colin <colin at southportweb.co.uk>
> Sender: owner-freebsd-gnome at freebsd.org
> 
> Kevin Oberman wrote:
> >> Date: Sun, 08 Nov 2009 18:19:05 +0000
> >> From: Colin <colin at southportweb.co.uk>
> >> Sender: owner-freebsd-gnome at freebsd.org
> >>
> >> Kevin Oberman wrote:
> >>     
> >>>> Date: Sun, 08 Nov 2009 11:59:16 +0000
> >>>> From: Colin <colin at southportweb.co.uk>
> >>>> Sender: owner-freebsd-gnome at freebsd.org
> >>>>
> >>>> Hi,
> >>>> I've been unable to upgrade libxslt for a while on my installation of 
> >>>> FreeBSD 7.0-RELEASE-p12
> >>>> It always tells me the following:
> >>>>
> >>>> checking for libxml libraries >= 2.6.27... configure: error: Version 
> >>>> 2.6.23 found. You need at least libxml2 2.6.27 for this version of libxslt
> >>>>
> >>>> I can find no information on where it is getting the information that 
> >>>> 2.6.23 is installed because pkg_info shows only libxml2-2.7.6 (the 
> >>>> current port) as installed.
> >>>>
> >>>> I don't really know anything about libxml2 so I assume there's some 
> >>>> leftover bits from an old version somewhere..can you point me in the 
> >>>> right direction to clean it up?
> >>>>     
> >>>>         
> >>> Just 'portupgrade -f libxml2' should do the trick. (Or what every tool
> >>> you would use to force the re-installation of a port). Then upgrade
> >>> libxslt. At least this has worked for me.
> >>>   
> >>>       
> >> Thanks for the reply Kevin,
> >> I have already done a full rebuild including recompiling libxml
> >> however I didn't use portupgrade. I've just tried the way you say and
> >> that has unfortunately not made any difference.
> >>
> >> Oh and as a side note, are there any archived for this list? The
> >> FreeBSD Gnome page lists freebsd-gnome and has a search box that
> >> points to a Russian site but I was wondering if there's a browseable
> >> archive?
> >>     
> >
> > Rats. This has always worked for me.
> >
> > The configure script, at about line 15800, does the check by issuing the
> > command 'xml2-config --version'. It should be using the xml2-config in
> > /usr/local/bin, but it does several operations to determine exactly what
> > command to use, so something might be causing it to use an old one.
> >
> > First, try entering '/usr/local/bin/xml2-config --version'. If that
> > reports the correct version, try 'locate xml2-config' to see if there is
> > another xml2-config on the system.
> >
> > Archives are found a number of places, but the official one is 
> > http://www.freebsd.org/community/mailinglists.html
> >   
> Apparently there are one or two old versions knocking around:
> 
> ted# /opt/xml2/bin/xml2-config --version
> 2.7.3
> ted# /usr/bin/xml2-config --version
> 2.6.23
> ted# /scripts/cpan_sandbox/x86_64/xml2-config --version
> 2.6.23
> ted# /root/installd/scripts/cpan_sandbox/x86_64/xml2-config --version
> 2.6.23
> ted# /usr/local/bin/xml2-config --version
> 2.7.6
> 
> The old versions must have either been installed from some other source 
> or not deleted properly by the ports during upgrade. What's the best way 
> to clean them up as I assume its best to only have the one version running!

Something rather odd has bitten your system. Thee is no reason that any
port would install files on /usr/bin. It looks to me like someone
installed libxml2 from place other than ports and it spattered stuff in
odd places.

/opt is a place several Unix-like systems install things. I know Solaris
does. The /root/installd and /scripts locations, I don't know
about. Since all are showing 2.6.23, all were probably done at the same
time.

One scheme would be to take the output of 'pkg_info -L libxml2-2.7.6 and
look for these files outside of /usr/local/. Time consuming, but could
be scripted fairly easily. Any of these files outside of /usr/local or
/usr/ports should be deleted.

Batter still would be to re-install world AFTER deleting the contents of
/usr/bin, /usr/include and /usr/lib and manually deleting
/etc/xml2Conf.sh if it is there. (Note that you will probably be unable
to run 'make installworld' after blowing away these directories, so you
will need to re-install them from another system. possibly a live
CD. I'll admit to never having tried this, though.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751