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

Re: 19990726: netCDF 3.4 on IBM SP/AIX 4.3 system using 64-bit addressing

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: 19990726: netCDF 3.4 on IBM SP/AIX 4.3 system using 64-bit addressing
  • Date: Mon, 26 Jul 1999 11:19:32 -0600
>To: address@hidden
>From: Mary Haley <address@hidden>
>Subject: netCDF 3.4 on IBM SP/AIX 4.3 system using 64-bit addressing
>Organization: National Center for Atmospheric Research
>Keywords: 199907261601.KAA24867

Hi Mary,

> I just thought I'd let you know that I tried compiling netCDF 3.4
> on our newest IBM SP machine which is running AIX 4.3. It compiled
> fine using the 32-bit addressing mode (-q32) but when I tried to
> use -q64 (should be the equivalent of using -64 on an SGI machine),
> I get the following message when I run "make test":
> 
> 
> .
> .
> .
> *** Testing nc_get_var_uchar ...  264 good comparisons. ok
> *** Testing nc_get_var_schar ...  269 good comparisons. ok
> *** Testing nc_get_var_short ...  682 good comparisons. ok
> *** Testing nc_get_var_int ...  1189 good comparisons. ok
> *** Testing nc_get_var_long ... 
>         FAILURE at line 1153 of test_get.c: value read not that expected
>         FAILURE at line 1153 of test_get.c: value read not that expected
 ...
>         FAILURE at line 1153 of test_get.c: value read not that expected
>  903 good comparisons. 
>         ### 286 FAILURES TESTING nc_get_var_long! ###
 ...
> In fact, all of the nc_*_long functions gave me some kind of error
> message
> when I ran "make test". I've attached both the compilation and test
> output 
> files in case you're interested.

Thanks for reporting this.

To debug this problem, we'll need access to NCAR's IBM SP on which to test
netCDF 3.5.  What's the name of the machine I should request a login
for?

--Russ