From 5edc686524a38fee76be4b99bf51cb1651a1f6f1 Mon Sep 17 00:00:00 2001 From: Olivier Certner Date: Fri, 5 Feb 2021 12:57:37 +0100 Subject: [PATCH] Issue #1699 - Follow-up: mozjemalloc: Fix build by excluding some irrelevant init_lock code This had been initially dealt with in issue #1699's commits, but one of them was in the end reverted, which caused this problem (this change should have been done there). --- memory/mozjemalloc/jemalloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memory/mozjemalloc/jemalloc.c b/memory/mozjemalloc/jemalloc.c index 71e568a0eb..01c559a2bb 100644 --- a/memory/mozjemalloc/jemalloc.c +++ b/memory/mozjemalloc/jemalloc.c @@ -5256,7 +5256,7 @@ malloc_init_hard(void) * Another thread initialized the allocator before this one * acquired init_lock. */ -#ifndef MOZ_MEMORY_WINDOWS +#if !(defined(MOZ_MEMORY_WINDOWS) || defined(__FreeBSD__)) malloc_mutex_unlock(&init_lock); #endif return (false);