Hi Robert,
Attached is the complete output, below is what I believe is the relevant
area of interest:
compiling C sources
creating build\temp.win-amd64-2.6\Release\build
creating build\temp.win-amd64-2.6\Release\build\src.win-amd64-2.6
creating build\temp.win-amd64-2.6\Release\build\src.win-amd64
I have used the trail of Visual Studio 2008 (on full Server 2003) it
copmiles and runs well if you comment out the lines meantioned earlier on in
this thread.
I am planning to spend some time with the intel fortran compiler to try to
compile blas/lapack in the next few weeks. It is part of my curr
Gael Varoquaux wrote:
>
> I was just wondering, could we ask Microsoft for some help here. A build
> bot, or a Windows 64 license... They are helping porting the SAGE project
> to windows, so they do have interest in getting open source scientific
> software working on windows.
>
Windows 64 is
On Sat, May 31, 2008 at 12:01:10PM +0900, David Cournapeau wrote:
> On Fri, May 30, 2008 at 8:35 PM, Hanni Ali <[EMAIL PROTECTED]> wrote:
> > I would also like to see a 64bit build for windows as well if possible.
> Unfortunately, this is difficult: windows 64 is not commonly available
> (I don'
Charles R Harris wrote:
>
> It probably just grew to fix problems as they arose. It should be
> possible to test for every function and fall back to the double
> versions that are more reliably present. It would be nicer if all
> compilers tried to conform to recent standards, i.e., be less than
Robert Kern wrote:
>
>
> There are a lot of them. Feel free to add any additional tests you
> think are necessary, and we'll see how painful it is at build-time.
>
What would be acceptable ? I quickly tested on my macbook, on mac os X:
it takes ~ 2 seconds / 25 functions tests. If speed really
On Tue, Jun 3, 2008 at 8:49 PM, David Cournapeau <
[EMAIL PROTECTED]> wrote:
> Robert Kern wrote:
> >
> > The presence of these functions should have been detected by the
> > configuration process of numpy. HAVE_FREXPF and HAVE_LDEXPF would have
> > been #define'd if we had detected them correctly
On Tue, Jun 3, 2008 at 9:49 PM, David Cournapeau
<[EMAIL PROTECTED]> wrote:
> Robert Kern wrote:
>>
>> The presence of these functions should have been detected by the
>> configuration process of numpy. HAVE_FREXPF and HAVE_LDEXPF would have
>> been #define'd if we had detected them correctly. It i
Robert Kern wrote:
>
> The presence of these functions should have been detected by the
> configuration process of numpy. HAVE_FREXPF and HAVE_LDEXPF would have
> been #define'd if we had detected them correctly. It is possible that
> our configuration process for this does not work correctly with
On Tue, Jun 3, 2008 at 3:21 AM, Hanni Ali <[EMAIL PROTECTED]> wrote:
> Hi David,
>
> I compiled numpy with MSVC 9.0 (vs 2008), I am just using the inbuilt LA
> libs to minimise complexity.
>
> Although I have hacked it such that I can compile and all but one of the
> regression tests passed:
>
> ==
Hi David,
I compiled numpy with MSVC 9.0 (vs 2008), I am just using the inbuilt LA
libs to minimise complexity.
Although I have hacked it such that I can compile and all but one of the
regression tests passed:
==
ERROR: Tests re
Excellenm, thanks for clearing all that up.
How about numpy with 2.6, any issues?
Hanni
2008/6/2 David Cournapeau <[EMAIL PROTECTED]>:
> Hanni Ali wrote:
> >
> > Yes I had used the internal versions in the mean time, but I do want
> > to try to use the intel fortran compiler in all likelyhood.
Hanni Ali wrote:
>
> Yes I had used the internal versions in the mean time, but I do want
> to try to use the intel fortran compiler in all likelyhood.
Yes, people can try to build as they want, that's the beauty of open
source :) But for official distribution, I don't want to depend on non
f
Hi David,
> I can't build official binaries with VS: I don't have VS. Also, there is
> the problem of building the fortran dependencies (BLAS/LAPACK). I don't
> know if it is even possible to build ATLAS on windows x64. Even assuming
> we only use netlib BLAS/LAPACK, I still need a fortran comp
Hanni Ali wrote:
>
> I had managed to compile and install 1.04 with vs 2005 64 bit with a
> bit of hacking,
I can't build official binaries with VS: I don't have VS. Also, there is
the problem of building the fortran dependencies (BLAS/LAPACK). I don't
know if it is even possible to build ATL
Hi David,
> Unfortunately, this is difficult: windows 64 is not commonly available
> (I don't have any access to it personally, for example), and mingw is
> not available yet for windows 64 either.
I had managed to compile and install 1.04 with vs 2005 64 bit with a bit of
hacking, however it h
On Fri, May 30, 2008 at 8:35 PM, Hanni Ali <[EMAIL PROTECTED]> wrote:
> I would also like to see a 64bit build for windows as well if possible.
>
>
Unfortunately, this is difficult: windows 64 is not commonly available
(I don't have any access to it personally, for example), and mingw is
not avail
I would also like to see a 64bit build for windows as well if possible.
Hanni
2008/5/30 Peter Creasey <[EMAIL PROTECTED]>:
> 2008/5/30 Peter Creasey <[EMAIL PROTECTED]>:
> > Is numpy v1.1 going to come out in egg format?
> >
>
> Oops, I didn't mean to mail with an entire numpy digest in the body
2008/5/30 Peter Creasey <[EMAIL PROTECTED]>:
> Is numpy v1.1 going to come out in egg format?
>
Oops, I didn't mean to mail with an entire numpy digest in the body.
sorry,
Peter
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://project
Is numpy v1.1 going to come out in egg format?
I ask because I only see the superpack installers on the sourceforge
page, and we have users who we are delivering to via egg - requires.
thanks,
Peter
2008/5/23 <[EMAIL PROTECTED]>:
> Send Numpy-discussion mailing list submissions to
>n
20 matches
Mail list logo
