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.
Jason, >Date: Wed, 29 Jan 2003 09:51:13 +1100 (EST) >From: Jason Roberts <address@hidden> >Organization: TPAC/Australia >To: Steve Emmerson <address@hidden> >Subject: Re: 20030128: problems with udunits on compaq system The above message contained the following: > The output I get from the make utlib.i is > > > cd lib > > make utlib.i > cc -E -I../port/misc -I../port/cfortran > -DUT_DEFAULT_PATH='"/short/e93/jlr581/udunits_test/udunits-1.11.7/etc/udunits.dat"' > -std utlib.c > utlib.i > > grep getenv utlib.i > path = getenv("UDUNITS_PATH"); I still don't like it because it indicates a problem with your development environment. A similar problem occurred later in your build: cc -c -O -I../port/misc -I../port/cfortran -DUT_DEFAULT_PATH='"/short/e93/jlr581/udunits-1.11.7/etc/udunits.dat"' -std udalloc.c cc: Warning: udalloc.c, line 34: In the initializer for mem, "malloc(...)" of type "int", is being converted to "pointer to void". (cvtdiftypes) voidp mem = malloc(nbytes); --------------------------^ I'm concerned that this might cause hard-to-diagnose problems and I want to eliminate it before progressing to mere guessing about what's wrong. Does the file port/misc/stdlib.h exist? If not, would you please look at the file /usr/include/stdlib.h and try to determine why its getenv() and malloc() declarations aren't being seen by the C compiler. Regards, Steve Emmerson <http://www.unidata.ucar.edu>