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.
Celia Chen wrote: > > Anne, > > I can't seem to figure out how c89 gets into each > Makefile! The c89s are back in the Makefiles > if I change all the c89s to gcc and run > ./configure again. (I also changed all the c89s and > ccs in the configure file to gcc before I ran ./configure.) > > BTW, on amber, /usr/bin/cc -> /etc/alternatives/cc and > /etc/alternatives/cc -> /usr/bin/gcc > > Celia Celia Chen wrote: > > Anne, > > I think the following two lines in config.cache define > CC in each Makefile after running configure: > > ac_cv_prog_CC=${ac_cv_prog_CC=gcc} > ac_cv_prog_CPP=${ac_cv_prog_CPP='gcc -E'} > > Celia > > Hi Celia, I'm sorry not to get back to you yesterday. Did your compilation finally succeed? The easiest way to change a variable for configure is to use 'setenv', e.g., do setenv CC gcc at the command line and then run configure. Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************