On Wed, Aug 22, 2012 at 3:14 PM, Nathaniel Smith <n...@pobox.com> wrote: > On Wed, Aug 22, 2012 at 11:40 AM, David Cournapeau <courn...@gmail.com> wrote: >> On Tue, Aug 21, 2012 at 12:15 AM, Chris Barker <chris.bar...@noaa.gov> wrote: >>> On Mon, Aug 20, 2012 at 3:51 PM, Travis Oliphant <tra...@continuum.io> >>> wrote: >>>> I'm actually not sure, why. I think the issue is making sure that the >>>> release manager can actually "build" NumPy without having to buy a >>>> particular compiler. >>> >>> The MS Express editions, while not open source, are free-to-use, and work >>> fine. >>> >>> Not sure what what do about Fortran, though, but that's a scipy, not a >>> numpy issue, yes? >> >> fortran is the issue. Having one or two licenses of say Intel Fortran >> compiler is not enough because it makes it difficult for people to >> build on top of scipy. > > There seems to be a 64-bit version of mingw -- I assume this runs into > the same issue that numpy has with new versions of 32-bit mingw? Would > it work if that issue were fixed?
It does have the same issue IIRC, but there was also the issue that scipy built with mingw-w64 did not work at all at that time. Could be different today, I have not looked into it for quite a while now. David _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
