A little more info:
To try and tease out the error, I run the cython compile step on my OSX machine to produce the appropriate .c extension files. I use that output on a linux machine and run
python setup.py install
which runs without Cython to try and install the package. But I get a very similar error on Linux (which I don't get on OSX):
...
running build_ext
Traceback (most recent call last):
File "/usr/lib/python2.7/pdb.py", line 1314, in main
pdb._runscript(mainpyfile)
...
File "/usr/local/lib/python2.7/dist-packages/setuptools/extension.py", line 45, in _convert_pyx_sources_to_lang
target_ext = '.cpp' if lang.lower() == 'c++' else '.c'
Uncaught exception. Entering post mortem debugging
Running 'cont' or 'step' will restart the program
> /usr/local/lib/python2.7/dist-packages/setuptools/extension.py(45)_convert_pyx_sources_to_lang()
-> target_ext = '.cpp' if lang.lower() == 'c++' else '.c'
(Pdb) p lang
['f', '7', '7', 'f', '7', '7']
Running the setup.py script under Pdb suggests that the variable `lang` should be a string instead of a list, so I'm not sure why that's happening. I'm also not sure if its reasonable that Fortran
is in the conversation, since my module is in C (although it does use blas and lapack).
Could this possibly be a Cython bug? More likely, I'm doing something wrong, but any help tracking it down would be appreciated.
Thanks,
AJ