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 3B5543858017; Wed, 27 Sep 2023 07:28:05 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3B5543858017
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1695799685;
	bh=abRBPx4UTiFutGCcRRVafWuj6vq6cWD065D/FI1M86s=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=f8o1HMZ41ak/J53hE7Z0LCG09N5CqBWDb9WpLaS23/6x+KnAyquAh4tmSOof+ooIm
	 Ku9JMaJ7cXL5pvJeluB1E4YQbRNVzD/ytfurZ6/1xymRn8g7SDNhZA+yqO3lkIDXuE
	 0ymg6Rhl13H7IlJUVCGz/jGt5Rv4z25lCoBjcZYA=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/111605] Cross compilation doesn't work with
 `-fuse-ld=mold`
Date: Wed, 27 Sep 2023 07:28:05 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: unknown
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: <bug-111605-4-vHwAn4ra5x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111605-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111605-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=3D111605

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is only a problem when using a cross gcc, so why should mold proactive=
ly
create symlinks for dozens of targets when mold is installed?

It seems to me that a single symlink only needs to be created by the person
building the cross-gcc, and installed alongside $target-gcc as part of that
toolchain. This is not mold's problem, and could just be documented as part=
 of
gcc's installation docs.

Although it probably does make sense for gcc to just fallback to using ld.m=
old
without the target prefix.=