Re: 20000107: Compiling problems with netcdf 3.4 and 3.5b on IRIX 6.5

Thorsten,

> To: address@hidden
> From: Thorsten Becker <address@hidden>
> Subject: Compiling problems with netcdf 3.4 and 3.5b on IRIX 6.5
> Organization: .
> Keywords: 200001071840.LAA20908

In the above message, you wrote:

> Hi,
> 
>       I am experiencing compiling trouble with netcdf version 3.5 beta
> which I have resorted to after having similar problems with version 3.4 (I
> thought that maybe portability issues had been resolved.) 
>       The problems arise because of a typedef statement in stddef.h
> which appears to try to redefine ptrdiff_t. I was not able to track down
> the origin of this problem, and I am rather certain that it is not related
> to any misconfiguration on our side. I would greatly appreciate any help
> with that matter. 
> 
>       Thank you in advance for your efforts, please find items A to F
> below as specified in the INSTALL document of your distribution.
> 
> Regards,
> 
> 
> Thorsten
> 
> 
> Log files and such:
> 
> A) uname -a
> 
> IRIX64 geophysics 6.5 10181059 IP27
> 
> (We have just updated our SGIs to the newest IRIX 6.5.)
> 
> B) cat VERSION
> 
> 3.5
> 
> C)  compilers:
> 
> /bin/cc
> /bin/f77
> /bin/CC
> 
> For compiler run logs, please disregard the annoying error messages about
> license problems, they are not at the root of the problem.

From your "make.log" file:

> Making `all' in directory /usr/geophysics/packages/netcdf-3.5/src/libsrc
> 
>         /bin/cc -c -O -n32 -mips4 -I.   attr.c
> 
> cc-1084 cc: ERROR File = /usr/include/stddef.h, Line = 37
>   The indicated declaration has an invalid combination of type specifiers.
> 
>   typedef int   ptrdiff_t;
>                 ^
> 
> cc-1084 cc: ERROR File = /usr/include/sys/types.h, Line = 219
>   The indicated declaration has an invalid combination of type specifiers.
> 
>   typedef int    ssize_t;

The errors above indicate a problem with your compilation environment: 
it appears that the C compiler can't use its own header files.  I suggest
you contact your system administrator and show them this problem.

Regards,
Steve Emmerson   <http://www.unidata.ucar.edu>