public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Mark Wielaard <mark@klomp.org>
Cc: buildbot@sourceware.org
Subject: Re: [PATCH 1/5] autoregen.py: enable autoreconf for gcc, libdecnumber, libiberty, libobjc
Date: Fri, 19 Apr 2024 10:21:38 +0200	[thread overview]
Message-ID: <CAPS5khbAze_OXOJdXCFevN=MTtFP8Vq3gPy463F=JwRLHWa+mA@mail.gmail.com> (raw)
In-Reply-To: <20240418215315.GF25080@gnu.wildebeest.org>

On Thu, 18 Apr 2024 at 23:53, Mark Wielaard <mark@klomp.org> wrote:
>
> On Wed, Apr 17, 2024 at 02:50:29PM +0000, Christophe Lyon wrote:
> > Calling just 'autoreconf' works well for these subdirs despite the
> > absence of Makefile.am: there's no real need to provide -I xxxx flags
> > when calling aclocal, the generated files are the same.
> >
> > It does make a difference for gcc and libobjc however: some warnings
> > are printed by autoreconf, because additional .m4 files are parsed in
> > a different order by plain 'aclocal' and 'aclocal -I xxx'.
> >
> > We can accept that for the buildbot, for the sake of simplicity of
> > this helper, but that may confuse users.
>
> Yeah, it is a little confusing. But hard to notice given the large
> number of warning in some of the other directories. Which is another
> problem when people run it by hand.
>

Yes, it's good to have the buildbot to confirm it sees the same
warnings as people see when running the tools by hand.

And I agree that these warnings should be fixed, but that's another problem :-)

Thanks,

Christophe

> Cheers,
>
> Mark

      reply	other threads:[~2024-04-19  8:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 14:50 Christophe Lyon
2024-04-17 14:50 ` [PATCH 2/5] autoregen.py: Move subdirs common to binutils-gdb and gcc Christophe Lyon
2024-04-17 14:50 ` [PATCH 3/5] autoregen.py: improve comment Christophe Lyon
2024-04-17 14:50 ` [PATCH 4/5] autoregen.py: libcpp can use autoreconf Christophe Lyon
2024-04-18 21:46   ` Mark Wielaard
2024-04-19  8:20     ` Christophe Lyon
2024-04-17 14:50 ` [PATCH 5/5] autoregen.py: Add introduction comment Christophe Lyon
2024-04-17 15:12   ` Simon Marchi
2024-04-18  9:59     ` Christophe Lyon
2024-04-18 21:55       ` Mark Wielaard
2024-04-19  8:22         ` Christophe Lyon
2024-04-18 21:53 ` [PATCH 1/5] autoregen.py: enable autoreconf for gcc, libdecnumber, libiberty, libobjc Mark Wielaard
2024-04-19  8:21   ` 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='CAPS5khbAze_OXOJdXCFevN=MTtFP8Vq3gPy463F=JwRLHWa+mA@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --cc=buildbot@sourceware.org \
    --cc=mark@klomp.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).