From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4A05C3858401; Thu, 18 May 2023 08:36:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4A05C3858401 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684399018; bh=+y5mfD0oOjWrZmTQ5tX4W+XZztTBVz7xMy2oVxZPihk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QRut3C+LdA8w96TOBXD477ebQ1FTr37pjw7P/slwPGPfE5JrHxJMkWMC6PyvDr/zA +bBgJGquOz5Kv/qgDi5jFE7BsEVzZir8Plc/sYLiMcKevQ24ubR6XI5rP0YCaykgxr 9a45w9WinV2hcCD2OFCOV+SJOhcz4Tsk67rB4IDE= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/109898] 'make install -j' sometimes corrupts 'dir' file for .info files due to parallel 'install-info' calls Date: Thu, 18 May 2023 08:36:55 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109898 --- Comment #2 from Jonathan Wakely --- (In reply to Sergei Trofimovich from comment #0) > --- gcc-12.2.0/gcc/Makefile.in 2022-08-19 10:09:52.280658631 +0200 > +++ gcc-12.2.0-new/gcc/Makefile.in 2023-05-04 14:35:44.401420184 +0200 > @@ -3781,6 +3781,11 @@ > fi; \ > fi >=20=20 > +# We don't care about the order in which the info files are built, but > +# install-info doesn't support multiple parallel invocations writing to > +# the same `dir-file`, so we have to disable parallelism for that reason: > +.NOTPARALLEL: install-info Prerequisites of .NOTPARALLEL are ignored, so doesn't this un-parallelize building the entire gcc sub-dir?=