From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 48A9C3858D33; Sun, 10 Sep 2023 06:34:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 48A9C3858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1694327653;
	bh=vuJrpkh+DSndBlr0zUSqIVh8OKNBe+BQJpBhJHS/XAs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=f0A/yNI84Herr+OoBhSzuFt3lIvmsffcYAfw3lXkqnt+tC2mtW27gn7RnNioVoJoz
	 G3b9XJ5UCCX4kiZW+K2RoY7U4UZNtMkA0XAL/OBAHrRFINji6lvOfFu2rj6eNre/xd
	 hFFk1/G05Ek8ohp9Wd6c/2Jx8vumZwo/ogmbRrcM=
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/106472] No rule to make target
 '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.
Date: Sun, 10 Sep 2023 06:34:13 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 12.1.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106472-4-9FsPnXAbPY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106472-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106472-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106472

--- Comment #30 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to matoro from comment #26)
> We also had somebody report on IRC that they observed this on powerpc (not
> sure what tuple), again with -j1.  It does not seem to show up with -j2, =
so
> likely -j1 is necessary to trigger.

I can also confirm that switching to -j2 makes this particular error go awa=
y=