Andrew Bennetts wrote:
> John: It's only complaining about the *_pyx extensions, not the *_c
> ones. So it appears that "make" probably was run, but that Pyrex isn't
> installed.
>
> Seeing as this appears to be a packaged copy of bzr, this is presumably
> a bug in the packaging rather than a mistake by Barry.
>
So in both cases unless '--allow-python-fallbacks' was set, 'make'
should fail if it cannot build the extensions (whether pyrex is
available or not).
I've certainly made use of that locally to do:
make && bzr selftest ...
So it may be that we need to look at the build chain, and figure out why
the builds are succeeding when they aren't getting the extensions built.
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
Andrew Bennetts wrote:
> John: It's only complaining about the *_pyx extensions, not the *_c
> ones. So it appears that "make" probably was run, but that Pyrex isn't
> installed.
>
> Seeing as this appears to be a packaged copy of bzr, this is presumably
> a bug in the packaging rather than a mistake by Barry.
>
So in both cases unless '--allow- python- fallbacks' was set, 'make'
should fail if it cannot build the extensions (whether pyrex is
available or not).
I've certainly made use of that locally to do:
make && bzr selftest ...
So it may be that we need to look at the build chain, and figure out why
the builds are succeeding when they aren't getting the extensions built.
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkr DYxgACgkQJdeBCY SNAAM/zgCgh1O93 MTYbX02x/ lr+QYi8UCw 4QatIGWnn60Os9y d8
xJcAoIJLbGYlLRD
=SVeG
-----END PGP SIGNATURE-----