Arfrever Frehtes Taifersar Arahesis, 09.06.2012 16:02:
2012-06-09 15:32:11 Stefan Behnel napisał(a):
F Wolff, 09.06.2012 14:35:
cc -fPIC -Wimplicit -I/usr/include/libxml2 -I/home/fwolff/download/python/lxml-lxml-2260f8d/src/lxml//include -I/home/fwolff/download/python/pypy-1.9/include -c src/lxml/lxml.etree.c -o build/temp.linux-i686-2.7/src/lxml/lxml.etree.o -w src/lxml/lxml.etree.c: In function ‘__pyx_f_4lxml_5etree_9_ErrorLog_connect’: src/lxml/lxml.etree.c:31030: error: ‘xmlStructuredErrorContext’ undeclared (first use in this function) src/lxml/lxml.etree.c:31030: error: (Each undeclared identifier is reported only once src/lxml/lxml.etree.c:31030: error: for each function it appears in.) error: command 'cc' failed with exit status 1
This is neither related to PyPy nor Cython. It's due to my rewrite of the error reporting code (intended to make it less intrusive when mixed with other users of libxml2), for which I accidentally used a feature that was only added in libxml2 2.7.4. That's too bad because this feature is rather crucial to the way error reporting should work. Guess I'll have to undo those changes, at least conditionally. I don't see how to make them work in those really old libxml2 versions that the current lxml releases still work with (even 2.7.4 has been out for almost three years now).
You could raise minimal required libxml2 version.
Well, yes, I'm aware of that. Raising it from 2.6.20 straight to 2.7.4, or rather 2.7.8 due to bugs in earlier versions, would be quite a step though, and it would definitely make some users unhappy. 2.6.x is still pretty widely used, from my experience. Stefan