summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorDan Nicholson <dbn.lists@gmail.com>2009-09-15 20:02:11 -0700
committerDan Nicholson <dbn.lists@gmail.com>2009-09-16 06:33:54 -0700
commita6bbc75162653e5a9a6a5504c62ee51be26e27a4 (patch)
tree8a5e2a2be27e1bcd5e5cef16fca7258b8b49a908 /src
parent638b006bd27416b2ebb5257a0aba8dd59e16f5a5 (diff)
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.
Diffstat (limited to 'src')
-rw-r--r--src/tet3/tcc/config.c1
-rw-r--r--src/tet3/tcc/proctc.c4
2 files changed, 5 insertions, 0 deletions
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: