[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20040415: netcdf-3.5.0.irix64-6.5-mips.tar.Z Bug

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20040415: netcdf-3.5.0.irix64-6.5-mips.tar.Z Bug
  • Date: Fri, 16 Apr 2004 13:50:28 -0600
>To: "'address@hidden'" <address@hidden>
>From: "Taylor, Ken" <address@hidden>
>Subject: netcdf-3.5.0.irix64-6.5-mips.tar.Z Bug
>Organization: FNMOC
>Keywords: 200404152153.i3FLrVCU010600

Hi Ken,

> I downloaded netcdf-3.5.0.irix64-6.5-mips.tar.Z because it was
> advertised as -64 ABI.  It actually is -n32 ABI.  Luckily, I was
> able to build the -64 ABI from the 3.5.1 source.

It was built on an irix64 system, where the default is still -n32 if
you don't specify -64 as a compile flag.

I checked the new binary

  ftp://ftp.unidata.ucar.edu/pub/binary/irix64_6.5-mips/netcdf-3.5.1.tar.Z

which was built on irix64 with the environment specified in

  ftp://ftp.unidata.ucar.edu/pub/binary/irix64_6.5-mips/netcdf-3.5.1.env

and it's also 32 bit objects, since that is still the default produced
by the irix64 compilers.  If we provided 64-bit objects, users compiling
with default flags would not be able to link to the resulting
libraries.  However we'll consider adding 64-bit binaries to the ones
we now have.  Thanks for reporting this.

--Russ