From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/108113] New: Rust and --enable-link-serialization=1
Date: Wed, 14 Dec 2022 19:49:29 +0000 [thread overview]
Message-ID: <bug-108113-35322@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108113
Bug ID: 108113
Summary: Rust and --enable-link-serialization=1
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rust
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org
Target Milestone: ---
Seems rust/Make-lang.in doesn't have link serialization support, I bet that
must break
--enable-link-serialization=1 builds with rust enabled.
See
r11-5142-gd326ebc94f3b2b0d962fb9e253564b39106a10da
r11-5190-ga774a6a2fbeaf7cbcb7a7afe433418f2d740b45b
commits what has been changed for other FEs.
The first change introduced some stuff that the second one reverted, so what is
needed
in rust/Make-lang.in is basically
rust.serial = rust1$(exeext)
and making
rust1$(exeext) depend on
$(rust.prev)
The generic code will ensure to fill in rust.prev to some other *.serial and
set some other *.prev to rust.serial as needed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-12-14 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 19:49 jakub at gcc dot gnu.org [this message]
2022-12-14 19:59 ` [Bug rust/108113] " dkm at gcc dot gnu.org
2022-12-14 21:01 ` dkm at gcc dot gnu.org
2022-12-16 18:35 ` tschwinge at gcc dot gnu.org
2022-12-19 8:54 ` dkm at gcc dot gnu.org
2022-12-19 11:42 ` tschwinge at gcc dot gnu.org
2022-12-19 11:49 ` jakub at gcc dot gnu.org
2022-12-20 8:12 ` cvs-commit at gcc dot gnu.org
2022-12-20 8:32 ` dkm 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-108113-35322@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@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).