From ef1004fdc0760e814295d96896b900ba2007df66 Mon Sep 17 00:00:00 2001 From: Matthew Flatt Date: Fri, 3 May 2019 12:57:58 -0600 Subject: [PATCH] cm: fix lock Commit 70e0cac0621 neglected to use `#:for-lock? #t` as intended. --- racket/collects/compiler/private/cm-minimal.rkt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/racket/collects/compiler/private/cm-minimal.rkt b/racket/collects/compiler/private/cm-minimal.rkt index 399784ca09..b4acfa2efe 100644 --- a/racket/collects/compiler/private/cm-minimal.rkt +++ b/racket/collects/compiler/private/cm-minimal.rkt @@ -706,7 +706,8 @@ (define lock-zo-name (if (cross-multi-compile? roots) ;; Make sure we use a file path for the lock that is consistent ;; with being in a phase of compiling for the current machine: - (path-add-extension (get-compilation-path path->mode roots path) #".zo") + (path-add-extension (get-compilation-path path->mode roots path #:for-lock? #t) + #".zo") zo-name)) ;; Called when `tryng-sha1?` is #f and this process (or some process) ;; needs to compile, recompile, or touch: