This problem has nothing to do with numpy -- somehow, gcc binaries
themselves were overwritten by a process that installed just 32-bit
versions, ... so the problem is with the c compiler itself, and has been
resolved.
thanks!
Dan
On Thu, Nov 11, 2010 at 7:48 AM, Dan Yamins wrote:
>
>
>
>> Yes,
> Yes, it should. This was fixed a couple of days ago in
> commit:435c7262592e94c8519f (master) and commit:8346ba04a5c574441304
> (1.5.x). I guess you used an older revision, can you please update and
> try again?
>
Did this, but am having the same problem.This is the relevant output at
the be
On Thu, Nov 11, 2010 at 3:37 AM, Dan Yamins wrote:
> Hi:
> I'm trying to build numpy with python27, 64-bit, on OSX 10.5.8.
> When I run python setup.py build, only 32-bit binaries get built. I can
> see what is happening is that not 64-bit flags are getting passed to the c
> compiler (I don't
> Are you sure that the python executable that you are using is the
> 64-bit python executable that you think it is?
>
Hm ... Well, I think so ... It certain is 64bit, or at least:
In [1]: import platform
In [2]: platform.architecture()
Out[2]: ('64bit', '')
Should I be checking something else?
On Wed, Nov 10, 2010 at 13:37, Dan Yamins wrote:
> Hi:
> I'm trying to build numpy with python27, 64-bit, on OSX 10.5.8.
> When I run python setup.py build, only 32-bit binaries get built. I can
> see what is happening is that not 64-bit flags are getting passed to the c
> compiler (I don't k
Hi:
I'm trying to build numpy with python27, 64-bit, on OSX 10.5.8.
When I run python setup.py build, only 32-bit binaries get built. I can
see what is happening is that not 64-bit flags are getting passed to the c
compiler (I don't know about the fortran compiler.
So I have two questions;
