From: Christophe Lyon <christophe.lyon@linaro.org>
To: FX Coudert <fxcoudert@gmail.com>
Cc: Iain Sandoe <iain@sandoe.co.uk>, gfortran <fortran@gcc.gnu.org>,
tkoenig@netcologne.de, gcc-patches@gcc.gnu.org,
tschwinge@baylibre.com, mark@klomp.org
Subject: Re: [PATCH] libgfortran: Fix up the autoreconf warnings.
Date: Thu, 2 May 2024 23:30:22 +0200 [thread overview]
Message-ID: <CAPS5khYOaacv_N-M54Cb0M-VMocK1e4u0qdEBhCYWX0rzR=ibA@mail.gmail.com> (raw)
In-Reply-To: <9DD52D29-10D0-4EC1-AF8D-A2EDA8AA573F@gmail.com>
On Thu, 2 May 2024 at 23:13, FX Coudert <fxcoudert@gmail.com> wrote:
>
> > libgfortran/ChangeLog:
> > * Makefile.am: Use sub-dirs, amend recipies accordingly.
> > * Makefile.in: Regenerate.
>
> Thanks Iain, I’ve tested it both with and without maintainer mode, and regenerated files with no issue. I can also confirm that the many autoreconf warnings that plagued libgfortran are now gone.
>
> Push as affd24bfc62203db9f9937c0d6cf8f1f75b80d72
>
Nice, I can see on Sourceware's buildbot that there is now zero
warning in libgfortran.
Thanks,
Christophe
> FX
prev parent reply other threads:[~2024-05-02 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 9:23 Iain Sandoe
2024-05-02 21:13 ` FX Coudert
2024-05-02 21:30 ` Christophe Lyon [this message]
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='CAPS5khYOaacv_N-M54Cb0M-VMocK1e4u0qdEBhCYWX0rzR=ibA@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=mark@klomp.org \
--cc=tkoenig@netcologne.de \
--cc=tschwinge@baylibre.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).