Per Johansson wrote:
> Ok, upgrade to latest pyrex version fixes the problem. The previous one
> was Pyrex-0.9.4-2.fc6, the new one is build from source, version
> 0.9.8.5.
>
There was a known bug in 0.9.4-? for which setup.py explicitly forbid
building using that version.
if have_pyrex and pyrex_version == '0.9.4.1':
It seems our version checking didn't include 0.9.4-2 or whatever you
were building with. If you could give us the result of:
from Pyrex.Compiler.Version import version
print version
We can add that version of the compiler to the black list. (My guess it
is either '0.9.4' or '0.9.4.0' or something along those lines.) Perhaps
we should just blacklist all of 0.9.4?
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Per Johansson wrote:
> Ok, upgrade to latest pyrex version fixes the problem. The previous one
> was Pyrex-0.9.4-2.fc6, the new one is build from source, version
> 0.9.8.5.
>
There was a known bug in 0.9.4-? for which setup.py explicitly forbid
building using that version.
if have_pyrex and pyrex_version == '0.9.4.1':
It seems our version checking didn't include 0.9.4-2 or whatever you
were building with. If you could give us the result of:
from Pyrex.Compiler. Version import version
print version
We can add that version of the compiler to the black list. (My guess it
is either '0.9.4' or '0.9.4.0' or something along those lines.) Perhaps
we should just blacklist all of 0.9.4?
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkr TVr0ACgkQJdeBCY SNAAMfzwCfe6Hhv ap4JtEfdUsZlwgu Zm7V yY2vNbeuLV3bCCV Gp
rBkAn2q2vopgWHG
=92vD
-----END PGP SIGNATURE-----