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 116183858004; Thu, 14 Sep 2023 09:21:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 116183858004
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1694683288;
	bh=OtQbJoofY4zwMzW4yNBlCKtRApqpEGrq1gG0K+h1cv8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=SGC0qB3J4ztfX0ZusgdRrKU0fv0XatVxB3yYsWpvhf/7f7e/kLb8xjw7iaESdaeON
	 //0HvgNNMu6ZzX+/zFrdXGCqzq2ohLGeeWHltiAT+FXhgjiIHaqbCEEllW8h9lwp0o
	 zn6xY5BH4fqjaXCLbQoLCHPSqeMepytF/ls4jraU=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/111406] libiberty build produces errors with CC=clang,
 unsupported option '-print-multi-os-directory'
Date: Thu, 14 Sep 2023 09:21:27 +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: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: <bug-111406-4-8X6GatwhLa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111406-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111406-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=3D111406

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
These are only used in the install targets which when bootstrapped will have
used GCC from earlier stages.  When building cross compilers we require GCC=
 as
host compiler.

So I think this isn't an issue unless you try to build libiberty stand-alone
or as part of binutils and also install it?

The sourceware bugzilla instance also doesn't have a libiberty component,
so tracking it here is possibly good enough but as said above you'll not hit
it in practice?=