Brian wrote:
> Greeting,
>
>
> I am trying to install numpy on the same system into to different
> prefixes, one dedicated to 32 bit stuff and the other to 64 bit. The
> machine is a dual CPU Core 2 Duo machine, that is a 64 bit native
> machine. Getting the 64 bit version to work is no pro
On Mon, Nov 3, 2008 at 10:46 AM, T J <[EMAIL PROTECTED]> wrote:
>
> Since these are all in the standard locations, I am building without a
> site.cfg. Here is the beginning info:
>
Apparently, this is not enough. Only if I also set the ATLAS
environment variable am I able to get this working as
Greeting,
I am trying to install numpy on the same system into to different
prefixes, one dedicated to 32 bit stuff and the other to 64 bit. The
machine is a dual CPU Core 2 Duo machine, that is a 64 bit native
machine. Getting the 64 bit version to work is no problem. But cross
compil
Numpy doesn't seem to be finding my atlas install. Have I done
something wrong or misunderstood?
$ cd /usr/lib
$ ls libatlas*
libatlas.a libatlas.so libatlas.so.3gf libatlas.so.3gf.0
$ ls libf77*
libf77blas.a libf77blas.so libf77blas.so.3gf libf77blas.so.3gf.0
$ ls libcblas*
libcblas.a lib
On Sun, Nov 2, 2008 at 12:23 PM, Paul Rudin <[EMAIL PROTECTED]> wrote:
>
> I'm experimenting with numpy and I've just written the code below, which
> computes the thing I want (I think). Self.bits is an RxRxR array
> representing a voxelized 3d model - values are either 0 or 1. I can't
> help thin
The fink guys fixed a bug so it now at least builds properly with
python 2.6.
-gideon
On Nov 3, 2008, at 1:35 AM, David Cournapeau wrote:
> Michael Abshoff wrote:
>>
>> Unfortunately numpy 1.2.x does not support Python 2.6. IIRC support
>> is
>> planned for numpy 1.3.
>>
>
> Also it is true i
Michael Abshoff wrote:
> Jarrod Millman wrote:
>
>> On Sat, Nov 1, 2008 at 1:07 AM, Robert Kern <[EMAIL PROTECTED]> wrote:
>>
>
> Hi,
>
>
>>> On Fri, Oct 31, 2008 at 05:25, David Cournapeau
>>> <[EMAIL PROTECTED]> wrote:
>>>
I was wondering whether it was really worth havi
