Whoops, I replied to this, but I sent only to Martijn by accident. Earlier message: I think it might also be good in general to call the xslt-config that is built by the buildout (the one in parts/libxslt/bin) whenever possible. I was having related issues on systems with no pre-installed xslt-config/headers with the deliverance buildout (which is based on the lxml buildout, thanks btw) There could theoretically be link flag differences as well if the system-wide/built-out versions had different dependencies. I wound up pushing parts/libxslt/bin onto the front of PATH with a recipe before calling lxmls setup, but there may be cleaner ways. There is a separate issue I mentioned in "lxml setup.py exslt link flag" related to doing this but I haven't gotten back to this yet to write a patch. If it helps, the deliverance buildout is at: http://codespeak.net/svn/z3/deliverance/buildout/trunk/ - Luke On Mon, 2006-11-20 at 16:40 -0600, Ian Bicking wrote:
Martijn Faassen wrote:
Hi there,
I reported previously that I created a buildout for lxml, but today I found out that is of limited utility: while it correctly links lxml against any libxml2 and libxslt library, it does still require the libxml and libxstl2 *headers* to be where xslt-config locates them, i.e. probably /usr/include
I tried to hack up the setup.py so it would look elsewhere (it is supposed to respond to things like --include-dirs), but setup.py has grown to be rather complicated. This is a common problem with configuring from Python code - it grows all kinds of things which look useful but also make it very hard to expect some kind of uniform behavior across different systems configuring themselves this way.
I hope that setup.py can still be adjusted so that buildout can be made to work. I *think* it's only not responding to --include-dirs that does it in.
Luke Tucker has been trying to resolve these same issues in the Deliverance buildout. I don't know the status -- hopefully he'll chime in -- but the work is in http://codespeak.net/svn/z3/deliverance/buildout/trunk