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.
Don, > I started over from tar, I think I followed all the instructions, and > managed to get rid of all the flags except the -DNO_STDARG, which seems to > cause the problem. Enclosed is my config.status. Thanks again. OK, that verifies that configure thinks the -DNO_STDARG flag is needed, but the gcc on our Solaris 2.4 systems doesn't need this flag. The flag says that a program with #include <stdarg.h> that tries to use facilities for variadic functions defined in the stdarg.h header file either gets a compiler error or generates some unexpected output when run. To further diagnose the problem, we'll need to see the output from compiling and running (if you get that far) the following 10-line program with gcc: #include <stdarg.h> main() { exit(0); } t() { ;} int foo(int bar, ...) { va_list alist; va_start(alist, bar); bar = (int)va_arg(alist, int); va_end(alist); return bar; } Just store the above program in a file, say "x.c", then run the following two commands to generate an executable "x" and to run it: gcc -o x x.c ./x These commands produce no output on our system (and should produce no output, if gcc is installed properly). If you get any output at all, please send it to us. Thanks. ______________________________________________________________________________ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu