From e5c7b44f7abf49170ffba98940c7c8bf95806d07 Mon Sep 17 00:00:00 2001 From: Joona Kiiski Date: Sat, 20 Dec 2014 08:51:53 +0000 Subject: [PATCH] Use "rm -f" instead of "rm" for gcc profiling hack in Makefile In some UNIX systems "rm" prompts user for confirmation. However "rm -f" is always a guaranteed forced deletion. Also move gcc profiling hack under the correct target No Functional change Resolves #168 --- src/Makefile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/Makefile b/src/Makefile index b641747a..a9715ec9 100644 --- a/src/Makefile +++ b/src/Makefile @@ -373,9 +373,6 @@ profile-build: @$(PGOBENCH) > /dev/null @echo "" @echo "Step 3/4. Building final executable ..." -# Deleting corrupt ucioption.gc* profile files is necessary to avoid an -# "internal compiler error" for gcc versions 4.7.x - @rm ucioption.gc* @touch *.cpp *.h syzygy/*.cpp syzygy/*.h $(MAKE) ARCH=$(ARCH) COMP=$(COMP) $(profile_use) @echo "" @@ -447,6 +444,9 @@ gcc-profile-make: all gcc-profile-use: +# Deleting corrupt ucioption.gc* profile files is necessary to avoid an +# "internal compiler error" for gcc versions 4.7.x + @rm -f ucioption.gc* $(MAKE) ARCH=$(ARCH) COMP=$(COMP) \ EXTRACXXFLAGS='-fbranch-probabilities' \ EXTRALDFLAGS='-lgcov' \ -- 2.39.2