public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-111605-4-vHwAn4ra5x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111605-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111605
--- 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 proactively
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.mold
without the target prefix.
next prev parent reply other threads:[~2023-09-27 7:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 4:31 [Bug c++/111605] New: " rui314 at gmail dot com
2023-09-27 4:35 ` [Bug driver/111605] " pinskia at gcc dot gnu.org
2023-09-27 5:00 ` rui314 at gmail dot com
2023-09-27 5:11 ` pinskia at gcc dot gnu.org
2023-09-27 5:17 ` rui314 at gmail dot com
2023-09-27 5:21 ` pinskia at gcc dot gnu.org
2023-09-27 5:30 ` rui314 at gmail dot com
2023-09-27 5:34 ` pinskia at gcc dot gnu.org
2023-09-27 5:38 ` rui314 at gmail dot com
2023-09-27 7:28 ` redi at gcc dot gnu.org [this message]
2023-09-27 7:37 ` rui314 at gmail dot com
2023-09-27 8:50 ` rguenth at gcc dot gnu.org
2023-09-27 9:06 ` rui314 at gmail dot com
2023-11-09 13:06 ` cvs-commit at gcc dot gnu.org
2023-11-09 13:08 ` rguenth at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111605-4-vHwAn4ra5x@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).