On 5/29/07, Mary Haley <haley@ucar.edu> wrote:

On Tue, 29 May 2007, Charles R Harris wrote:

> On 5/29/07, Mary Haley <haley@ucar.edu> wrote:
>>
>>
>> Hi all,
>>
>> I have been trying to build numpy 1.0.3 on my SGI/IRIX64 box (64-bit
>> version) with no luck.  I'm using Python 2.4.4.
>
>
> There have been other reports of problems on IRIX 6.5. What we need is
> someone running on an SGI box and willing to help us get things working.

Chuck,

I will be willing to help here. Unfortunately I can't give people logins
to this system, but I will be willing to try a bunch of things.

> I've tried setting CC to both the default "cc" compiler (which
>> I built python with), and "gcc", with no luck.  I tried c89 and c99,
>> still with no luck. I get errors like:
>>
>> cc -64 _configtest.o -L/usr/local/lib -L/usr/lib -o _configtest
>> ld64: FATAL   12 : Expecting n64 objects: /usr/lib/crt1.o is o32.
>> ld64: FATAL   12 : Expecting n64 objects: /usr/lib/crt1.o is o32.
>
>
> Looks like ld is trying to link a 64bit program to a 32bit library. I wonder
> what crt1 is? Is there a 64bit version? How are the 64 and 32 bit libraries
> in IRIX distinguished?

I was wondering about this /usr/lib/crt1.o myself.

Google yields:

... crt1.o is the "c run time object" which gets prepended to
your files when you compile them so they can run when you type their
names if you have the permissions set correctly.

 
I am not sure why this would show up in numpy as numpy is compiling to a module Hmmm.

Chuck.