Project's Makefiles run with no builtin rules or variables

Until now, after removing all environment variables, we were just giving
Make the top Makefile to execute. By default, for every target, Make will
try many built-in rules (which is good when compiling programs, but
redundant in other cases). All these checkings also populate the debugging
output of Make (with `-d'). So its easier and slightly faster to just tell
Make to ignore builtin rules and variables.

With this commit, to address this issue, the `project' script runs
`.local/bin/make' with `--no-builtin-rules' and `--no-builtin-variables'.

1 files changed, 2 insertions, 1 deletions

diff --git a/project b/project
index ee3bff3..c5b2cdd 100755
--- a/project
+++ b/project
@@ -230,7 +230,8 @@ controlled_env() {
     # Remove all existing environment variables (with `env -i') and only
     # use some pre-defined environment variables, then build the project.
     envmake=".local/bin/env -i HOME=$bdir sys_rm=$(which rm) $gopt"
-    envmake="$envmake .local/bin/make -f $1"
+    envmake="$envmake .local/bin/make --no-builtin-rules"
+    envmake="$envmake --no-builtin-variables -f $1"
     if ! [ x"$debug" = x  ]; then envmake="$envmake --debug=$debug"; fi
 
     # Set the number of jobs. Note that for the `configure.sh' script the