This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: How to stop gcc caching
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: richardcavell at mail dot com
- Cc: gcc-help at gcc dot gnu dot org
- Date: Sun, 6 Mar 2011 12:46:57 +0000
- Subject: Re: How to stop gcc caching
- References: <8CDA9BC9AE43E38-1F30-4537@web-mmc-d01.sysops.aol.com>
On 6 March 2011 02:23, <richardcavell@mail.com> wrote:
> Hi everyone.
>
> My project is about 3500 lines in 75 .c files and 75 .h files. ?I have a
> makefile that compels gcc to compile all of these files every time. ?It only
> takes a few seconds.
>
> I have noticed, though, that sometimes when I change one of the source
> files, gcc doesn't take the change into account right away. ?If I edit the
> file in gedit, it'll be okay, but if I transfer a new version of a file
> using the GNOME GUI, for example, gcc doesn't appear to know that the file
> has changed. ?It either uses an old version of the file or an old object
> file. ?Yet my directory doesn't contain any .o files.
>
> How is gcc caching its input or output? ?How do I turn it off?
It's not. GCC doesn't do anything like that.
What do you mean by transfer a new file using the GNOME GUI? Are you
transferring from another machine? Could the clocks be out of sync, so
the "new" file has an older timestamp (that shouldn't matter if your
makefile really rebuilds everything every time, but maybe it's not.)