Just to note, on the compilation issue, I encountered this a while ago with numpy 1.1.1 and I think Python 2.6b2, again because we wanted to skip Python 2.5 in my organization, largely because it was an issue to get working on 64-bit. I couldn't find anywhere 7.1 was available. We discussed errors you are encountering a few months ago, they are related to the compiler directives.
#ifndef HAVE_FREXPF static float frexpf(float x, int * i) { return (float)frexp((double)(x), i); } #endif #ifndef HAVE_LDEXPF static float ldexpf(float x, int i) { return (float)ldexp((double)(x), i); } #endif
Commenting out this section at line 64 allow compilation and has no ill
effects.
Hanni
2008/10/8 David Cournapeau
Ravi wrote:
The reasons above are why I don't try to do anything on Windows unless
there
is support from some external source, e.g., CMake taking care of build issues. The reasons above are also why I admire your heroic efforts at making Windows binaries available. But, then, I sometimes wonder about the motivation for an unpaid volunteer to take on an utterly thankless job in which help is never forthcoming from users;
I think numpy and scipy have a wonderful potential, and that currently, installation is the biggest hurdle. I can show some awesome things in numpy/scipy and co that people used to matlab would only dream of. But if it takes more than 2 minutes and a few clicks to install, it is of no use. I have some people who ask me how to install numpy/scipy, and I have no simple answer: I think this is by far the biggest barrier of entry for numpy and scipy ATM. That's why I am interested in making numpy and scipy installation easy.
Thank for taking on this arduous task.
Just want to mention I am certainly not the only one involved here for windows binaries. This is really a collective work,
cheers,
David _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion