Michael Guntsche wrote:
On Jan 2, 2009, at 21:34, Ian Bicking wrote:
Martin (copied) has been having a problem building Deliverance/lxml on a Mac using the latest static build stuff. Given the error messages (http://paste.plone.org/25648 for /usr/bin/python and http://paste.plone.org/25646 with macports Python), it seems like it might be related to the architecture. The compilation uses "-arch ppc -arch i386" pretty much unconditionally (in buildlibxml.py).
Right now the Deliverance installation procedure is a bit opaque in this regard, so we couldn't really try just editing buildlibxml.py and rerunning. But I'm wondering why both -arch options are always there? Is the macports Python also a fat binary, or should it be contingent on which Python we're using?
Both static libs are build as universal binary. If you have a python build that is NOT Universal only the lib for your arch will be linked during compilation. I just tested current trunk with an universal python build (downloaded from python.org) and a i386 macports version and both worked without errors. Looking at the the messages shows that there is something else going on, maybe it would be helpful to just see if lxml itself can be build on this system.
It definitely can, in that I have built it using this recipe: http://pypi.python.org/pypi/z3c.recipe.staticlxml I'm afraid I don't really understand how binary egg builds work in general, or the static lxml build works in particular, so I can't be very helpful beyond that. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book