[Bug bootstrap/93548] gcc build tries to modify source tree

[jakub at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93548

Jakub Jelinek  changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu.org

--- Comment #5 from Jakub Jelinek  ---
Created attachment 47767
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47767&action=edit
gcc10-pr93548.patch

IMHO we should use move-if-change and be happy even if gcc_update has not be
run, only require it is actually regenerated if something changed.

[Bug bootstrap/93548] gcc build tries to modify source tree

[bernd.edlinger at hotmail dot de]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93548

Bernd Edlinger  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #4 from Bernd Edlinger  ---
thanks, seems to work now.

[Bug bootstrap/93548] gcc build tries to modify source tree

[bernd.edlinger at hotmail dot de]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93548

--- Comment #3 from Bernd Edlinger  ---
Ah, thanks I will do that.
Apparently the git conversion is to blame :)

[Bug bootstrap/93548] gcc build tries to modify source tree

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93548

--- Comment #2 from Jonathan Wakely  ---
Do you use contrib/gcc_update to update timestamps of generated files so they
don't need to be regenerated?

[Bug bootstrap/93548] gcc build tries to modify source tree

[bernd.edlinger at hotmail dot de]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93548

--- Comment #1 from Bernd Edlinger  ---
git Revision c3ccce5b47f85d70127f5bb894bc5e83f8d2510e

If absolutely necessary that should only be done in maintainer mode.