From a6bbc75162653e5a9a6a5504c62ee51be26e27a4 Mon Sep 17 00:00:00 2001 From: Dan Nicholson Date: Tue, 15 Sep 2009 20:02:11 -0700 Subject: tcc: Don't create locks unless told to In the typical situation, there is no reason to create the tet_lock files. Especially since tcc wants to put them in the source directory, which might not be writable. --- src/tet3/tcc/config.c | 1 + src/tet3/tcc/proctc.c | 4 ++++ 2 files changed, 5 insertions(+) (limited to 'src') diff --git a/src/tet3/tcc/config.c b/src/tet3/tcc/config.c index 842d3bde..36b015ba 100644 --- a/src/tet3/tcc/config.c +++ b/src/tet3/tcc/config.c @@ -1172,6 +1172,7 @@ int mode; int bv_len; } bvar[] = { { "TET_EXEC_IN_PLACE" }, + { "TET_EXEC_LOCK" }, { "TET_OUTPUT_CAPTURE" }, { "TET_API_COMPLIANT" }, { "TET_PASS_TC_NAME" }, diff --git a/src/tet3/tcc/proctc.c b/src/tet3/tcc/proctc.c index 6b98a872..0dc1292f 100644 --- a/src/tet3/tcc/proctc.c +++ b/src/tet3/tcc/proctc.c @@ -584,6 +584,10 @@ register struct proctab *prp; char *altexecdir; int shared; + /* see if we should create locks at all */ + if (!getmcflag("TET_EXEC_LOCK", prp->pr_currmode)) + return 0; + /* see if we should create shared or exclusive locks */ switch (prp->pr_currmode) { case TCC_EXEC: -- cgit v1.2.3