Hi, all, There was a patch to remove libgcc_tm.stamp when developers manually issue "make clean-target-libgcc" (under top-level build folder) or "make clean" (under BUILD-FOLDER/TARGET/libgcc).
Without that patch, we cannot successfully do "make all-target-libgcc" again due to that we remove libgcc_tm.h but not libgcc_tm.stamp. It would complain nonexistence of libgcc_tm.h during the libgcc building process: fatal error: libgcc_tm.h: No such file or directory According to the discussion thread last year, I thought it has been committed into gcc-4_7-branch: http://gcc.gnu.org/ml/gcc-patches/2012-05/msg01630.html http://gcc.gnu.org/ml/gcc-patches/2012-05/msg01636.html But by checking out 4.7 branch repository, I notice that it is only committed into the trunk (r187838) on that time. Since gcc-4_7-branch is still open and there will be 4.7.4 release, is it OK to backport r187838 into gcc-4_7-branch? libgcc/ChangeLog 2013-05-09 Chung-Ju Wu <jasonw...@gmail.com> Backport from mainline 2012-05-24 Olivier Hainque <hain...@adacore.com> * Makefile.in (clean): Remove libgcc_tm.stamp as well. Use a separate command for stamp removals. Index: libgcc/Makefile.in =================================================================== --- libgcc/Makefile.in (revision 198729) +++ libgcc/Makefile.in (working copy) @@ -121,7 +121,8 @@ .PHONY: all clean clean: - -rm -f config.h libgcc_tm.h stamp-h stmp-ldirs libgcc.map + -rm -f config.h libgcc_tm.h libgcc.map + -rm -f libgcc_tm.stamp stamp-h stmp-ldirs -rm -f *$(objext) -rm -f *.dep -rm -f *.a Best regards, jasonwucj
