From: Richard Biener <rguenther@suse.de>
To: Arthur Cohen <arthur.cohen@embecosm.com>
Cc: gcc-patches@gcc.gnu.org, gcc-rust@gcc.gnu.org,
Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>
Subject: Re: [PATCH 2/2] gccrs: fixup: Fix missing build dependency
Date: Thu, 11 Jan 2024 15:23:28 +0100 (CET) [thread overview]
Message-ID: <s5q428q1-sr3n-pp05-437r-9940nn9rs80o@fhfr.qr> (raw)
In-Reply-To: <20240111142355.1110429-4-arthur.cohen@embecosm.com>
On Thu, 11 Jan 2024, Arthur Cohen wrote:
> From: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>
>
> Fix the missing dependency between the gcc and libgrust.
>
> ChangeLog:
>
> * Makefile.def: Add a dependency to libgrust for all-gcc.
> * Makefile.in: Regenerate the file.
>
> Signed-off-by: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>
> ---
> Makefile.def | 1 +
> Makefile.in | 10 ++++++++++
> 2 files changed, 11 insertions(+)
>
> diff --git a/Makefile.def b/Makefile.def
> index 1a256db5518..19954e7d731 100644
> --- a/Makefile.def
> +++ b/Makefile.def
> @@ -375,6 +375,7 @@ dependencies = { module=configure-gcc; on=all-ld; };
> dependencies = { module=configure-gcc; on=all-gold; };
> dependencies = { module=configure-gcc; on=all-libiconv; };
> dependencies = { module=all-gcc; on=all-libiberty; hard=true; };
> +dependencies = { module=all-gcc; on=all-libgrust; };
That looks wrong? Why is libgrust both a host and a target module?
Is that really necessary? IIRC the rust frontend isn't written in
rust?
The other patch is OK to push.
> dependencies = { module=all-gcc; on=all-gettext; };
> dependencies = { module=all-gcc; on=all-mpfr; };
> dependencies = { module=all-gcc; on=all-mpc; };
> diff --git a/Makefile.in b/Makefile.in
> index 263b979609b..edb0c8a9a42 100644
> --- a/Makefile.in
> +++ b/Makefile.in
> @@ -67558,6 +67558,16 @@ all-stagetrain-gcc: all-stagetrain-libiberty
> all-stagefeedback-gcc: all-stagefeedback-libiberty
> all-stageautoprofile-gcc: all-stageautoprofile-libiberty
> all-stageautofeedback-gcc: all-stageautofeedback-libiberty
> +all-gcc: maybe-all-libgrust
> +all-stage1-gcc: maybe-all-stage1-libgrust
> +all-stage2-gcc: maybe-all-stage2-libgrust
> +all-stage3-gcc: maybe-all-stage3-libgrust
> +all-stage4-gcc: maybe-all-stage4-libgrust
> +all-stageprofile-gcc: maybe-all-stageprofile-libgrust
> +all-stagetrain-gcc: maybe-all-stagetrain-libgrust
> +all-stagefeedback-gcc: maybe-all-stagefeedback-libgrust
> +all-stageautoprofile-gcc: maybe-all-stageautoprofile-libgrust
> +all-stageautofeedback-gcc: maybe-all-stageautofeedback-libgrust
> all-gcc: maybe-all-gettext
> all-stage1-gcc: maybe-all-stage1-gettext
> all-stage2-gcc: maybe-all-stage2-gettext
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH,
Frankenstrasse 146, 90461 Nuernberg, Germany;
GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)
next prev parent reply other threads:[~2024-01-11 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 14:22 [PATCHSET] Fix Rust bootstrap for future libgrust changes Arthur Cohen
2024-01-11 14:22 ` [PATCH 1/2] gccrs: fixup: Fix bootstrap build Arthur Cohen
2024-01-11 14:22 ` [PATCH 2/2] gccrs: fixup: Fix missing build dependency Arthur Cohen
2024-01-11 14:23 ` Richard Biener [this message]
2024-01-11 14:32 ` Arthur Cohen
2024-01-11 14:30 ` Richard Biener
2024-01-12 0:02 ` [PATCHSET] Fix Rust bootstrap for future libgrust changes Thomas Schwinge
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=s5q428q1-sr3n-pp05-437r-9940nn9rs80o@fhfr.qr \
--to=rguenther@suse.de \
--cc=arthur.cohen@embecosm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=pierre-emmanuel.patry@embecosm.com \
/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).