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

Re: 19990107: building under HP-UX B.10.20: size_t undefined

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: 19990107: building under HP-UX B.10.20: size_t undefined
  • Date: Thu, 07 Jan 1999 10:22:38 -0700
Ken,

>Date: 07 Jan 1999 11:58:44 -0500
>From: Ken Waters <address@hidden>
>Organization: NOAA/NWS/Southern Region HQ
>To: address@hidden
>Subject: Re[2]: 19990107: building under HP-UX 10.20
>Keywords: 199901062300.QAA00661

In the above message, you wrote:

>      You're right about running under csh.  I went ahead and followed your 
>      directions and attached the results to this email.  BTW, thanks for 
>      the tip on combining output under csh.  
>      
>      Ken
> 
> making `dynamic' in directory /home/briefer/netcdf-perl-1.2/src/perl
> 
>       cc -c -I/home/briefer/netcdf-3.4/include -D_HPUX_SOURCE 
> -I/usr/local/include -O     -DVERSION=\"1.2\"  -DXS_VERSION=\"1.2\"  
> -I/opt/perl5/lib/PA-RISC1.1/5.00401/CORE  NetCDF.c
> (Bundled) cc: warning 480: The -O option is available only with the C/ANSI C 
> product; ignored.
> (Bundled) cc: "/home/briefer/netcdf-3.4/include/netcdf.h", line 195: error 
> 1000: Unexpected symbol: "size_t".
...
> *** Error exit code 1
> 
> Stop.
> *** Error exit code 1
> 
> Stop.
> *** Error exit code 1
> 
> Stop.
> *** Error exit code 1
> 
> Stop.

Puzzling.  The netCDF header-file <netcdf.h> includes <stddef.h> with
is required by the C Standard to define "size_t" (and does on our HP-UX
B.11.00 system and did on our HP-UX B.10.20 system).  Apparently,
however, it doesn't on yours.

I don't recall ever seeing that error message about the "-O" option.
What's the absolute pathname of your "cc" compiler?  (Try executing the
command "which cc".)

Look at the <stddef.h> header-file associated with your "cc" compiler
(NB: it might *not* be in "/usr/include").  Does it define "size_t"?  Is
it bracketed by conditional compilation directives.  If so, what are the
macros that are being tested?

Does your "cc" compiler have an option for making it a Standard C
compiler (e.g. "-Aa")?

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