This repository has been archived by the owner on May 13, 2020. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
something is wrong there with libxslt, log more output
- Loading branch information
Showing
1 changed file
with
4 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
68266f6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there really something wrong with libxslt?
The lxml 3.3.0 build currently fails because of a bug in lxml, that is already fixed in master. When lxml 3.3.1 comes out to PyPI, the wineggbuilder should be able to build it fine.
68266f6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might have been distracted by
http://winbot.zope.org/builders/wineggbuilder/builds/48385/steps/release%20eggs/logs/stdio
68266f6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's very confusing :-(
The Windows build procedure doesn't use xslt-config.
I'm probably explaining this to the person who wrote the code to implement that procedure ;)
68266f6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But lxml's script uses it.... and outputs that errors. That's confusing.