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

20000731: config.cache file

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: 20000731: config.cache file
  • Date: Mon, 31 Jul 2000 17:12:25 -0600
Mary,

"make distclean" will remove all Makefile and config output.
You should use this option whenever you want to start building from scratch.

Steve Chiswell


>From: Mary Haley <address@hidden>
>Organization: National Center for Atmospheric Research
>Keywords: 200007312254.e6VMs4T19101

>
>Hi,
>
>I was curious about something: is it possible to have the config.cache
>file removed when one does a "make clean"?  I build netCDF for several
>different systems, but I only keep one copy of the source lying around.
>If I forget to remove config.cache, then I end up getting the wrong
>compiler options.
>
>Normally I wouldn't get bitten by this, because if I have a leftover
>config.cache
>from another machine, I will get error messages right away. But I
>recently got bitten
>when I built netCDF on the same machine that I previously built it on,
>but I went from
>64-bit mode to 32-bit mode and forgot to remove the config.cache file. 
>I built netCDF
>unaware that it was setting my size of longs to 8 bytes (along with some
>other settings
>that are different between the two modes).
>
>I realize the config.cache file is a handy file.  Am I the only one that
>gets bitten
>by being forgetful and not removing it?  :-)
>
>
>
>--Mary Haley
>address@hidden
>