I stuck this code in at the end of the ext_modules list in setup.py:
Extension("pyrna",  ["pyrna.pyx"],library_dirs=['/home/thomas/
ViennaRNA-1.7/lib'],
               libraries=['RNA'],include_dirs=['/home/thomas/
ViennaRNA-1.7/H'])
After I pasted that in I realized I was mixing quotes, and changed the
first two arguments to 'pyrna' and 'pyrna.pyx'.  It compiled fine
after I made this change.  It's unclear to me why it worked in the
initial huge build, but I'm glad it's working.  Thank you both for the
swift replies.
Thomas

On May 21, 7:41 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> On May 22, 2:04 am, tkeller <[EMAIL PROTECTED]> wrote:
>
> Hi Thomas,
>
> > You were correct, it doesn't try to rebuild everything, just modules
> > that have changed.  However, I am now getting the following error
> > message:
> > running build_ext
> > building 'pyrna' extension
> > error: unknown file type '.pyx' (from 'pyrna.pyx')
> > sage: There was an error installing modified sage library code.
>
> Do you link any C/C++ glue code in there? Can you post the exact code
> you use to build the extension? Often this is solved by "touching" the
> extension that setup.py complains about.
>
> > This error didn't occur during the first, complete build.  The only
> > thing I changed was adding a dummy function so that it would rebuild
> > the module.  Removing it doesn't affect the error, so I don't think it
> > is that.
> > Thomas
>
> <SNIP>
>
> Cheers,
>
> Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to