I am way out of my element trying to build numpy on Windows, but we
are having a replicable (though somewhat inconsistently on some
machines) problem using fmin_cg on Windows that I am trying to debug.
I'm on Windows 7 64-bit with Python 2.6.4
First, I try to build numpy. It complains about havi
Albert Strasheim wrote:
> Hello
>
> I took a quick look at the code, and it seems like new_fcompiler(...) is too
> soon to throw an error if a Fortran compiler cannot be detected.
>
> Instead, you might want to return some kind of NoneFCompiler that throws an
> error if the build actually tri
Hello all
- Original Message -
From: "David M. Cooke" <[EMAIL PROTECTED]>
To: "Discussion of Numerical Python"
Sent: Thursday, May 31, 2007 2:53 AM
Subject: Re: [Numpy-discussion] build problem on Windows (was:
buildproblemon RHE3 machine)
> On Thu, May
On Thu, May 31, 2007 at 02:32:21AM +0200, Albert Strasheim wrote:
> Hello all
>
> - Original Message -
> From: "David M. Cooke" <[EMAIL PROTECTED]>
> To: "Discussion of Numerical Python"
> Sent: Thursday, May 31, 2007 2:08 AM
> Subject:
Hello all
- Original Message -
From: "David M. Cooke" <[EMAIL PROTECTED]>
To: "Discussion of Numerical Python"
Sent: Thursday, May 31, 2007 2:08 AM
Subject: Re: [Numpy-discussion] build problem on Windows (was: build
problemon RHE3 machine)
> On Wed, May
On Wed, May 30, 2007 at 03:06:04PM +0200, Albert Strasheim wrote:
> Hello
>
> I took a quick look at the code, and it seems like new_fcompiler(...) is too
> soon to throw an error if a Fortran compiler cannot be detected.
>
> Instead, you might want to return some kind of NoneFCompiler that thro
Hello
I took a quick look at the code, and it seems like new_fcompiler(...) is too
soon to throw an error if a Fortran compiler cannot be detected.
Instead, you might want to return some kind of NoneFCompiler that throws an
error if the build actually tries to compile Fortran code.
Cheers,
Al
