[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
: 20000419: Binaries for IRIX (fwd)
- Subject: : 20000419: Binaries for IRIX (fwd)
- Date: Wed, 19 Apr 2000 13:52:47 -0600
Art,
My C compiler is 7.2.3.1, yours is 7.1.
Ours system administrator called SGI andthey said that there were some
major changes in the 7.2 version that were not backwards compatible.
I placed out libc.so.1 in the irix binary directory. If you want to
see if this solves you problems, then download this into the
$GEMLIB directory and set the LD_LIBRARY_PATH environmental variable
to the $GEMLIB directory so that the loader will search there for the
C library. You will need to create a link from libc.so.1 to libc.so
as well in that directory as well. I don't know if other libraries
might crop up with incompatibilities- but at least you can give this a shot.
If this doesn't work, then it would suggest that we can't provide binaries
that will reliably run on old OS versions.
Steve Chiswell
Unidata User Support
---------- Forwarded message ----------
Date: Wed, 19 Apr 2000 13:11:46 -0600
From: Mike Schmidt <address@hidden>
To: address@hidden
Subject: Re: 20000419: Binaries for IRIX
Chiz,
I've called SGI, and their position is that compiling -o32 might be
backwards compatible and might run (with respect to older OS versions),
but it's not supported. I see the global symbol in the library ...
% nm /lib/libc.so.1 | grep -i libc_attr
[15303] | 263516468| |Global | |Data | __libc_attr
In a jam, I'd say ftp over our newer libc.so and test/run the software
against that lib until they can rebuild or upgrade.
mike
On Apr 19, 9:48am, Unidata Support wrote:
> Subject: 20000419: Binaries for IRIX
>
>
> Mike,
>
> I tried compiling some GEMPAK IRIX binaries for Penn State
> (I use the -o32 flag), they are running IRIX 6.3 on an O2
> which is not IRIX64.
>
> Some programs fail to launch with an unresolved __libc_attr
> message.
> ...