Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jonathan Wakely via Gdb <gdb@sourceware.org>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: Mark Wielaard <mark@klomp.org>,
	overseers@sourceware.org, gcc@gcc.gnu.org,
	 binutils@sourceware.org, gdb@sourceware.org,
	libc-alpha@sourceware.org,
	 "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: Updated Sourceware infrastructure plans
Date: Fri, 19 Apr 2024 10:35:49 +0100	[thread overview]
Message-ID: <CAH6eHdShkkyCFLf1ZbQa5Q0=x24gugN0wx7vOrkSB5NiEyhALQ@mail.gmail.com> (raw)
In-Reply-To: <5bde614c-224f-4ec6-8450-7c0911938cf9@netcologne.de>

On Thu, 18 Apr 2024 at 07:06, Thomas Koenig via Gcc <gcc@gcc.gnu.org> wrote:
>
> Am 18.04.24 um 01:27 schrieb Mark Wielaard:
> > We also should make sure that all generated files (either in git or in
> > the release/snapshot tar balls) can be reliably and reproducibly
> > regenerated. This also helps the (pre-commit) CI buildbots. We already
> > have the autoregen bots for gcc and binutils-gdb. And Christoph has
> > been working on extending the scripts to regenerate more kinds of
> > files.
>
> I regenerate auto* files from time to time for libgfortran. Regenerating
> them has always been very fragile (using --enable-maintainer-mode),
> and difficult to get right.

I've been curious for ages why gfortran requires using maintainer mode
for that. Nobody else uses maintainer mode for GCC development, so it
causes friction when somebody has to do changes across the whole of
gcc including gfortran parts.

If it doesn't work with a simple autoreconf then that should be fixed.

  parent reply	other threads:[~2024-04-19  9:41 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 23:27 Mark Wielaard
2024-04-18  6:04 ` Thomas Koenig via Gdb
2024-04-18  8:14   ` FX Coudert via Gdb
2024-04-18  9:01     ` Christophe Lyon via Gdb
2024-04-18 11:38     ` Janne Blomqvist via Gdb
2024-04-18 12:01       ` Generated files in libgfortran for Fortran intrinsic procedures (was: Updated Sourceware infrastructure plans) Tobias Burnus
2024-04-18 12:32         ` Martin Uecker via Gdb
2024-04-19  9:35   ` Jonathan Wakely via Gdb [this message]
2024-04-18 15:56 ` Updated Sourceware infrastructure plans Joseph Myers via Gdb
2024-04-18 17:37   ` Frank Ch. Eigler via Gdb
2024-04-18 17:54     ` Joseph Myers via Gdb
2024-04-18 18:29     ` Matt Rice via Gdb
2024-04-22 15:39     ` Tom Tromey
2024-04-23  2:55       ` Jason Merrill via Gdb
2024-04-23  3:12         ` Simon Marchi via Gdb
2024-04-23  3:24         ` Tom Tromey
2024-04-23  3:51           ` Jason Merrill via Gdb
2024-04-23  8:56             ` Mark Wielaard
2024-04-23  9:39               ` Richard Earnshaw (lists) via Gdb
2024-04-23 15:08             ` Tom Tromey
2024-04-23 15:25               ` Simon Marchi via Gdb
2024-04-24  8:49                 ` Aktemur, Tankut Baris via Gdb
2024-04-23  4:06           ` Ian Lance Taylor
2024-04-23  9:30           ` Richard Earnshaw (lists) via Gdb
2024-04-23 13:51             ` Ian Lance Taylor via Gdb
2024-05-01 19:15           ` Jeff Law via Gdb
2024-05-01 19:38             ` Jonathan Wakely via Gdb
2024-05-01 20:20               ` Mark Wielaard
2024-05-01 20:53                 ` Tom Tromey
2024-05-01 21:04                   ` Simon Marchi via Gdb
2024-05-02 15:35                     ` Pedro Alves
2024-05-02 23:05                       ` Fangrui Song
     [not found]                       ` <DS7PR12MB57651DA3A5C22B2847C13580CB182@DS7PR12MB5765.namprd12.prod.outlook.com>
2024-05-07 16:17                         ` Joseph Myers via Gdb
2024-05-10 10:43                           ` Ben Boeckel via Gdb
2024-05-01 20:04             ` Jason Merrill via Gdb
2024-05-01 21:26               ` Mark Wielaard
2024-05-01 22:01                 ` Sergio Durigan Junior via Gdb
2024-05-02 12:54                 ` Claudio Bantaloukas via Gdb
2024-05-02 15:33                 ` Pedro Alves
2024-05-03  2:59                   ` Ian Lance Taylor
2024-05-04 19:56                 ` Ben Boeckel via Gdb
2024-05-05  5:22                   ` Benson Muite via Gdb
2024-05-06 13:58                     ` Ben Boeckel via Gdb
2024-05-07 16:26                   ` Joseph Myers via Gdb
2024-05-01 21:38               ` Jeff Law via Gdb
2024-05-02  6:47                 ` Richard Biener via Gdb
2024-05-02 11:29                   ` Ian Lance Taylor via Gdb
2024-05-02 14:26                   ` Simon Marchi via Gdb
2024-05-02 11:45                 ` Mark Wielaard
2024-05-01 22:56               ` Tom Tromey
2024-04-23 10:34         ` Florian Weimer via Gdb
2024-04-22 10:01   ` Mark Wielaard
2024-04-22 13:23     ` Joseph Myers via Gdb
2024-04-19  9:33 ` Jonathan Wakely via Gdb
2024-04-22 10:24   ` Mark Wielaard
2024-04-22 11:40     ` Jonathan Wakely via Gdb
2024-04-23  0:48   ` Frank Ch. Eigler via Gdb

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='CAH6eHdShkkyCFLf1ZbQa5Q0=x24gugN0wx7vOrkSB5NiEyhALQ@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.org \
    --cc=overseers@sourceware.org \
    --cc=tkoenig@netcologne.de \
    /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