[Pyrex] Pyrex testing

[Scott Jackson]

Furthermore, I've come up with a productive bug- I get a series of these
when I run the tests:

Running test Tests/Bugs/other/watts2.pyx
gcc: unrecognized option `-no-cpp-precomp'
cc1: warning: unrecognized gcc debugging option: m
cc1: invalid option `no-fused-madd'
cc1: unrecognized option `-Wno-long-double'
Traceback (most recent call last):
  File "Testing.py", line 176, in run_compile_test
    result.object_file = c_compile(result.c_file)
  File
"/home/builder/programs/lib/python2.5/site-packages/Pyrex-0.9.5.1a.001.dev200707251128-py2.5.egg/Pyrex/Unix/LinuxSystem.py", line 56, in c_compile
    raise CCompilerError("C compiler returned status %s" % status)
CCompilerError: C compiler returned status 1
TEST FAILED: C compiler failed.

At any rate, I can diff you my version of the test suite in its mangled
and hacked state if you'd like.

On Fri, 2007-07-27 at 12:48 +1200, Greg Ewing wrote:
> Scott Jackson wrote:
> > $ ./bin/run_tests
> > /usr/bin/env: pythonw: No such file or directory
> > ===
> > So I change it to 'python':
> 
> Hmmm. I'm not sure why I used pythonw there -- it
> shouldn't be necessary.
> 
> > ===
> > $ ./bin/run_tests
> > Traceback (most recent call last):
> >   File "./bin/run_tests", line 6, in <module>
> >     from Pyrex.Testing import Testing
> > ImportError: No module named Testing
> 
> You may need to adjust your PYTHONPATH so that it
> makes the Pyrex directory available as an importable
> package.
> 
-- 
Scott Jackson <scott.jackson at enthought.com>
Enthought, Inc.