On 2008-07-13 , at 09:51 , Chris Janton wrote:
> We "moved some files around" on a server
>
> I have a "fresh" install of libxml2
>
> sudo port install libxml2
>
> worked fine...
I went looking to see if I could discover what was wrong. Forgive me
for not remembering the exact tickets I read, but...
I decided to install a *really* old version of libxml2 and try again
(it's a really old OS). I chose libxml2 2.6.21
I got the Portfile from trac.macports.org, put it into a local
directory then did
sudo port uninstall -f libxml2
sudo port uninstall libxslt
sudo port install
now I have an "old" version of libxml2 installed.
Re-did the php5 install
sudo port clean --work php5
sudo port install php5 +apache +macosx +mysql5 +pear
everything seems to be back to "normal", but I am using an ancient
libxml2.
Looking at the Portfiles for the old version of libxml2 and the new I
see this difference
2.6.21 --
configure.args --mandir=${prefix}/share/man --with-iconv=$
{prefix} \
--enable-static=no \
--without-python
2.6.32 --
configure.args --disable-static \
--without-python
Not sure if this helps. Not sure if I am going to get "bit" by
anything, but all of our "standard" things are back working again.
If anyone can help "fix" my brain so I can come closer to
understanding what is/was happening, that would be great.
Yes - 10.3.9 is somewhat painful. Still don't have the choice to move
forward. Wondering when I have to stop doing any port updates/syncs.
8)
----------------------------------
Chris Janton - face at CentosPrime dot COM
Netminder for Opus1.COM
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
