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

960416: Bad test result under Ultrix

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: 960416: Bad test result under Ultrix
  • Date: Tue, 16 Apr 96 14:06:15 -0600
Charles,

>Date: Tue, 16 Apr 1996 15:54:26 -0400 (EDT) 
>From: address@hidden (Charles Packer)
>Organization: NASA/GSFC
>To: address@hidden (Steve Emmerson)
>Subject: Re: 960416: Bad test result under Ultrix 
>Keywords: 199604152011.AA25912

In the above message you wrote:

> Here is what the config.log looks like when compiler is the default "cc":
> 
> -----------------------------------------------------------
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> ccom: Warning: (null), line 1: standard C not fully supported
> ccom: Warning: (null), line 1: standard C not fully supported
> ccom: Warning: /usr/include/stdio.h, line 185: "const" not yet implemented
>       extern FILE *     fopen( const char *__filename, const char *__type );
>       ------------------------------------^
> ccom: Warning: /usr/include/stdio.h, line 185: "const" not yet implemented
>       extern FILE *     fopen( const char *__filename, const char *__type );
>       ------------------------------------------------------------^
> ccom: Warning: /usr/include/stdio.h, line 186: "const" not yet implemented
>       extern int        fprintf( FILE *__stream, const char *__format, ... );
> .
> .
> .
> -----------------------------------------------
> 
> It's not clear to me here whether "not fully supported"
> means that your configure has sniffed out a deficiency in
> the Ultrix C compiler or that your configure is not fully
> supporting C...

It means that the C compiler is sub-standard.

Nothing in the above lines indicates why the `int' and `long' sizes
would be 0.  To determine that, we'd probably have to edit the configure
script and start manually compiling, linking, and executing the test
programs it creates.  Since you've already solved the problem of
building the package, this is probably more work than can be justified.

Feel free to contact me if you want to pursue this or if you have any
other questions.

--------
Steve Emmerson   <address@hidden>