Hi Istvan, anyone else, can you give me some pointers on compiling Pygr on Windows? It looks like I am able to compile Python extension modules (e.g. from pygr import cnestedlist raises no errors), but basic POSIX functionality like fdopen() appears to fail on this platform (Windows XP Professional, compiling with mingw32; see details below). For example in pygr.seqfmt.read_fasta_lengths(), fdopen() on a file descriptor returns NULL, i.e. it fails to open a stream, so SequenceFileDB objects appear to be empty (it fails to index any of the sequences in the database). Based on running the test suite, my setup only seems to run the pure Python parts of Pygr correctly; the extension modules are not working for me.
If someone has Pygr compiling successfully on Windows, please tell me how to set that up. Thanks!!! FYI, here is my setup: - Windows XP Professional installed in a VMWare Fusion 2.0.4 virtual machine, running on my Macbook Pro. - Python 2.5.4 installed via the standard windows installer - mingw 5.1.4 installed using their automatic installer, including gcc 3 (not gcc 4) - Pyrex 0.9.8.5 - I used pexports / libtool to replace the libpython25.a in C: \Python25\libs, as people on the web said was necessary to enable mingw32 to compile Python extensions. Is that correct? Other pages seem to say that the gcc 3 in mingw may have problems which might be related to the fdopen() failure... Another guy on the web says he has fixed gcc 4 in mingw to compile Python extensions properly... On the other hand gcc 4 is only available as a mingw alpha release... Marek seems to be seeing the same problems on his Windows XP PC, using a similar Python / mingw setup (see his details below). Yours, Chris Begin forwarded message from Marek Szuba: > On Wed, 15 Apr 2009 19:37:35 -0700 > Christopher Lee <l...@chem.ucla.edu> wrote: > >> can you tell me exactly what you had to do get Python extension >> modules to build properly with mingw? I ran into the whole "Python >> 2.5 was compiled with MS visual studio..." problem and followed >> advice on the web to replace libpython25.a with one built using >> pexports / libtool. Combining that with the --compiler=mingw32 seems >> to build extension files, which Python can import without complaint. >> However, I don't think the extensions are working properly -- tones >> of tests fail. > I'm actually in a very similar situation as you - the only thing I've > done differently is the pexports / libtool step, since I read this > has no longer been necessary since Python 2.5 was released. Result - > everything builds fine but there are many errors, plus Python crashes > when I reach NLMSA tests. > > -- > MS --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
