From 0b4c4cf2110d79a508913c8fed0e5b49accd5541 Mon Sep 17 00:00:00 2001
From: Laurent Rineau <Laurent.Rineau__CGAL@normalesup.org>
Date: Mon, 21 Jun 2010 20:15:35 +0000
Subject: [PATCH] Well, lockfile is probably not what we want, but let's keep
 its use and work-around its behavior: chmod u+x the created file.

---
 Scripts/developer_scripts/autotest_cgal | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Scripts/developer_scripts/autotest_cgal b/Scripts/developer_scripts/autotest_cgal
index b72e77ae6a9..eee4b1dcbe3 100755
--- a/Scripts/developer_scripts/autotest_cgal
+++ b/Scripts/developer_scripts/autotest_cgal
@@ -880,8 +880,10 @@ if [ ${?} != 0 ]; then
     fi
   fi
 fi
+# Make that file writable (lockfile create read-only files
+chmod u+x "$LOCK_FILE"
 # Put the PID of current process in the lock file
-echo $$ >> "$LOCK_FILE"
+echo $$ > "$LOCK_FILE"
 
 # that line makes the script remove the lock file in case of unwanted exit
 trap "rm -f $LOCK_FILE" EXIT HUP INT TERM