Hi Ned. I've removed the mac ports version of libxml2 and libxslt and it compiled - woo hoo!! I'll try a new build of mod_python tomorrow. Maybe things are not so bad after all. This is quite encouraging. I guess I am getting down about these linking issues and of course want some better reliability back into some of the software builds that I seemed to have before. Many thanks for this tip :-)
Regards David Ned Deily wrote: > In article <[EMAIL PROTECTED]>, > David Pratt <[EMAIL PROTECTED]> wrote: >> I will be attempting to build mod_python again shortly and will report >> back of my experience. I might try a different compiler also to test if >> it does not work to see if it makes a difference. In my gut, I am >> beginning to feel despite my best effort to keep the software of my >> machine up to date, my PPC is becoming a paper weight. This has really >> got me frustrated since my machine has still got plenty of life and I >> believed universal meant that PPC hardware users were not going to be >> left out in the cold. It has been an excellent development machine up to >> the time Universal build was introduced. I am running into similar >> linking issues with lxml. See below. What can be done about this :-( > > FWIW, lxml builds and runs just fine using easy_install on my PPC with > the latest universal build pythonmac 2.5.1 on 10.4.9. One obvious > difference apparent from your log file: on my system lxml is linking > with the Apple-supplied libxml2, libxslt, and libexslt in /usr/lib/, not > whatever you have in /opt/local/lib (presumably libs installed by port?). > _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
