public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: 20230920120311.14892-3-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 3/3] build: Regenerate build files
Date: Thu, 21 Sep 2023 10:55:10 +0200	[thread overview]
Message-ID: <ZQwE7hlOOl2sglvL@tucnak> (raw)
In-Reply-To: <20230921084600.40546-2-arthur.cohen@embecosm.com>

On Thu, Sep 21, 2023 at 10:44:30AM +0200, Arthur Cohen wrote:
> From: Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>
> 
> Resending this patch without most of the diff so it fits on the ML.
> 
> -----
> 
> Regenerate all build files.
> 
> ChangeLog:
> 
> 	* Makefile.in:

Missing Regenerate. above?

> 	* configure: Regenerate.
> 	* libgrust/Makefile.in: New file.
> 	* libgrust/aclocal.m4: New file.
> 	* libgrust/configure: New file.
> 	* libgrust/libproc_macro/Makefile.in: New file.
> 
> libgm2/ChangeLog:
> 
> 	* Makefile.in: Regenerate.
> 	* aclocal.m4: Regenerate.
> 	* libm2cor/Makefile.in: Regenerate.
> 	* libm2iso/Makefile.in: Regenerate.
> 	* libm2log/Makefile.in: Regenerate.
> 	* libm2min/Makefile.in: Regenerate.
> 	* libm2pim/Makefile.in: Regenerate.

	Jakub


  reply	other threads:[~2023-09-21  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21  8:44 Arthur Cohen
2023-09-21  8:55 ` Jakub Jelinek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-20 11:59 [PATCH 1/3] librust: Add libproc_macro and build system Arthur Cohen
2023-09-20 11:59 ` [PATCH 3/3] build: Regenerate build files Arthur Cohen

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=ZQwE7hlOOl2sglvL@tucnak \
    --to=jakub@redhat.com \
    --cc=20230920120311.14892-3-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).