Re: contrib/gcc_update bug?

[Richard Earnshaw <rearnsha at arm dot com>]

> Richard Earnshaw wrote:
> > 
> > This can happen if gcc_update is itself updated and the change includes an
> > alteration in the list of things to touch.  Maybe gcc_update could be made
> > intelligent enough to detect this; I don't know.  In the mean time, if
> > gcc_update is changed by an update, it is best to run it again.
> 
> Very plausible.  Not true.  Remember, I did a complete pull and *then*
> ran the update.  The likely cause is that gcc_update is *missing*
> a file name that needs touching.  This be a bug.  :)

Oops.  Sorry, I misread what you had written.  I don't know why, but I 
*thought* you had said that after doing the update you had the bug, but 
then after running the "touch" it went away.  That would have been 
consistent with what I had written.

Yes, I agree.  It looks like a new file needs adding to the touchlist.

R.