fixed in 2.0.5-1, doesn't need to be fixed in cython.
** Changed in: lxml (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: cython (Ubuntu)
Status: New => Invalid
--
[jaunty] lxml FTBFS on all platforms
https://bugs.launchpad.net/bugs/308633
You received this bug notifica
> gcc generates different code depending on which version is used. Sometimes,
> using one gcc version can result in a crash, while other gcc versions work
> just fine. Does that make GCC unstable software?
GCC is available as a versioned package in the distribution, so you have
the choice of using
> Debian wants to be able to build from source, and be able to change the
> source; if this cannot be done, then lxml has to be removed from Debian.
It can be done, lxml should generally work just fine with the latest
release version of Cython. It's just that using a different version won't
yield
> regarding lxml recompilation:]
> I hope the Debian package users of lxml are happy with untested,
> unreleased sources. Cython is a quickly moving target that can generate
> very different code from one day to another. lxml is rarely released with
> C code generated from an official Cython releas
Invalidating this bug in the Cython project, as it's really not a bug
there.
** Changed in: cython
Status: New => Invalid
--
[jaunty] lxml FTBFS on all platforms
https://bugs.launchpad.net/bugs/308633
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
[regarding lxml recompilation:]
I hope the Debian package users of lxml are happy with untested,
unreleased sources. Cython is a quickly moving target that can generate
very different code from one day to another. lxml is rarely released with
C code generated from an official Cython release, so reg
** Changed in: lxml (Ubuntu)
Importance: Undecided => Low
Status: New => Confirmed
--
[jaunty] lxml FTBFS on all platforms
https://bugs.launchpad.net/bugs/308633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Attached is a patch that fixes the FTBFS problem with lxml. What I've
done is to avoid the recompilation of the *.pyx files with cython, thus
removing the need for cython in Build-Depends.
Cythonizing the *.pyx files was introduced as a bug-fixing measure
because of a bug in one of the .pyx files.
Since 2.1.1-2.1 lxml packaging was changed to always re-compile the
*.pyx files (see
http://packages.debian.org/changelogs/pool/main/l/lxml/current/changelog )
--
[jaunty] lxml FTBFS on all platforms
https://bugs.launchpad.net/bugs/308633
You received this bug notification because you are a membe
During installation, Cython now compiles some of its own modules into C
extensions to speed up compilation (by quite a bit, actually). If it
can't import them for some reason (e.g. they were built for a different
Python version), you will get the error above.
BTW, this does not affect lxml as long
Not solved yet, but this is a far as I've come. I've done some
experiments on my cleanroom jaunty sbuilder.
* The error does NOT happen when the package is built with cython_0.9.8-1. Thus
it seems to be a regression in cython_0.10.2-1
* The error happens when setup.py is run by the -dbg version o
11 matches
Mail list logo
