[lxml-dev] 2.2.2 binary egg for Mac OS X 10.6
Hi, We have binary eggs for Python 2.4, 2.5 and 2.6 on Mac OS X 10.5. Unfortunately, we don't have them for 10.6 (Snow Leopard), and the 10.5 egg doesn't work on 10.6 (it crashes on startup). Is there any chance we could have 10.6 eggs? If there are reliable build instructions, I can help build them. Cheers, Martin
Martin Aspeli <optilude <at> gmail.com> writes:
Is there any chance we could have 10.6 eggs? If there are reliable build instructions, I can help build them.
I've tried this, and it hasn't been easy. :) - I first tried from the svn tag, but I couldn't get Cython to install. It complained about int or double size (I don't have the error anymore) - I then tried from the source .tar.gz, with python setup.py build --static- deps. That failed with compiler errors until I re-installed XCode with the OS X 10.4 compatibility library - I saw some advice about linking /usr/bin/gcc to gcc-4.0 instead of gcc-4.2, but that caused other platform issues in the build process - With gcc 4.2, the new XCode, and --static-deps it now builds cleanly, but when I try to run the tests I get: $ python test.py Traceback (most recent call last): File "test.py", line 595, in ? exitcode = main(sys.argv) File "test.py", line 558, in main test_cases = get_test_cases(test_files, cfg, tracer=tracer) File "test.py", line 260, in get_test_cases module = import_module(file, cfg, tracer=tracer) File "test.py", line 203, in import_module mod = __import__(modname) File "/Users/optilude/tmp/python/lxml/lxml-2.2.2/src/lxml/html/ __init__.py", line 12, in ? from lxml import etree ImportError: Failure linking new module: /Users/optilude/tmp/python/lxml/lxml-2.2.2/src/lxml/etree.so: Symbol not found: _htmlParseChunk Referenced from: /Users/optilude/tmp/python/lxml/lxml- 2.2.2/src/lxml/etree.so Expected in: flat namespace in /Users/optilude/tmp/python/lxml/lxml-2.2.2/src/lxml/etree.so I also tried to use the egg in my application, and got: $ ./bin/test plone.z3cform Test-module import failures: Module: plone.z3cform.tests Traceback (most recent call last): File "/Users/optilude/Development/Plone/Code/Build/dexterity/src/ plone.z3cform/plone/z3cform/tests.py", line 12, in ? import z3c.form.testing File "/Users/optilude/.buildout/eggs/z3c.form-2.1.0- py2.4.egg/z3c/form/testing.py", line 42, in ? import lxml.html File "build/bdist.macosx-10.6-i386/egg/lxml/html/__init__.py", line 12, in ? File "build/bdist.macosx-10.6-i386/egg/lxml/etree.py", line 7, in ? File "build/bdist.macosx-10.6-i386/egg/lxml/etree.py", line 6, in __bootstrap__ ImportError: Failure linking new module: /Users/optilude/.python-eggs/ lxml-2.2.2-py2.4-macosx-10.6-i386.egg-tmp/lxml/etree.so: Symbol not found: _exsltRegisterAll Referenced from: /Users/optilude/.python-eggs/ lxml-2.2.2-py2.4-macosx-10.6-i386.egg-tmp/lxml/etree.so Expected in: flat namespace in /Users/optilude/.python-eggs/ lxml-2.2.2-py2.4-macosx-10.6-i386.egg-tmp/lxml/etree.so At this point, I don't know what else to try. Google is not giving me many clues. :) Any ideas? Martin
Martin Aspeli <optilude <at> gmail.com> writes:
Is there any chance we could have 10.6 eggs? If there are reliable build instructions, I can help build them.
Okay, I finally got this to work using zc.buildout and z3c.recipe.staticlxml. I have eggs for Python 2.4 and 2.6. The build for Python 2.5 is failing in mysterious ways (it says "no egg found" in the temp directory). Can I have PyPI access (username 'optilude') to upload these? Otherwise, can I send them somewhere for someone else? Martin
Martin Aspeli wrote:
Martin Aspeli <optilude <at> gmail.com> writes:
Is there any chance we could have 10.6 eggs? If there are reliable build instructions, I can help build them.
Okay, I finally got this to work using zc.buildout and z3c.recipe.staticlxml.
I have eggs for Python 2.4 and 2.6. The build for Python 2.5 is failing in mysterious ways (it says "no egg found" in the temp directory).
Can I have PyPI access (username 'optilude') to upload these? Otherwise, can I send them somewhere for someone else?
Actually, I'm not sure that these *do* work. I think I need to defer to Stefan Eletzhofer or someone else with a bit more experience of doing this right. It is really frustrating. People get stuck on this almost on a daily basis trying to use some of the new Plone tools we have that depend on lxml. :( I realise it's not lxml's fault, but unfortunately it's something that lxml will have to fix, since Apple aren't going to. ;-) Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book
participants (2)
-
Martin Aspeli -
Martin Aspeli