From: "Richard Earnshaw \(lists\) via Gdb" <gdb@sourceware.org>
To: Christophe Lyon <christophe.lyon@linaro.org>, joel@rtems.org
Cc: Jan Beulich <jbeulich@suse.com>,
Richard Biener <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>,
binutils@sourceware.org, GCC Mailing List <gcc@gcc.gnu.org>,
gdb@sourceware.org, Nick Clifton <nickc@redhat.com>,
Joel Brobecker <brobecker@adacore.com>,
Carlos O'Donell <carlos@redhat.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Thiago Bauermann <thiago.bauermann@linaro.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: Patches submission policy change
Date: Mon, 8 Apr 2024 16:37:25 +0100 [thread overview]
Message-ID: <0e5ff742-8990-4338-a1a7-fb431aff9280@arm.com> (raw)
In-Reply-To: <CAPS5khY87xRqsE8G7UE2BAcfa2rhv_K8jBKF-sE4ONYcy0b-3g@mail.gmail.com>
On 03/04/2024 14:23, Christophe Lyon via Gcc wrote:
> On Wed, 3 Apr 2024 at 14:59, Joel Sherrill <joel@rtems.org> wrote:
>>
>> Another possible issue which may be better now than in years past
>> is that the versions of autoconf/automake required often had to be
>> installed by hand. I think newlib has gotten better but before the
>> rework on its Makefile/configure, I had a special install of autotools
>> which precisely matched what it required.
>>
>> And that led to very few people being able to successfully regenerate.
>>
>> Is that avoidable?
>>
>> OTOH the set of people touching these files may be small enough that
>> pain isn't an issue.
>>
>
> For binutils/gcc/gdb we still have to use specific versions which are
> generally not the distro's ones.
That's because at least some distros modify autoconf to their own taste/needs, so that it does not generate the same output as the officially released version. Furthermore, they provide no mechanism to make their version revert back to the original behaviour.
R.
next prev parent reply other threads:[~2024-04-08 15:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 8:22 Christophe Lyon via Gdb
2024-04-03 8:30 ` Jan Beulich via Gdb
2024-04-03 13:11 ` Christophe Lyon via Gdb
2024-04-04 8:12 ` Jan Beulich via Gdb
2024-04-05 7:22 ` Christophe Lyon via Gdb
2024-04-03 8:45 ` Jakub Jelinek via Gdb
2024-04-03 8:49 ` Jan Beulich via Gdb
2024-04-03 8:57 ` Richard Biener via Gdb
2024-04-03 10:21 ` Jan Beulich via Gdb
2024-04-03 12:58 ` Joel Sherrill
2024-04-03 13:23 ` Christophe Lyon via Gdb
2024-04-08 15:37 ` Richard Earnshaw (lists) via Gdb [this message]
2024-04-03 12:59 ` Jason Merrill via Gdb
2024-04-03 13:19 ` Christophe Lyon via Gdb
2024-04-03 9:50 ` Jonathan Wakely via Gdb
2024-04-03 15:03 ` Simon Marchi via Gdb
2024-04-04 21:35 ` Mark Wielaard
2024-04-04 21:51 ` Simon Marchi via Gdb
2024-04-05 6:44 ` Marc via Gdb
2024-04-05 7:17 ` Christophe Lyon via Gdb
2024-04-06 16:29 ` Mark Wielaard
2024-04-07 12:32 ` Jonathan Wakely via Gdb
2024-04-07 14:02 ` Mark Wielaard
2024-04-07 14:20 ` Jonathan Wakely via Gdb
2024-04-07 22:00 ` Mark Wielaard
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=0e5ff742-8990-4338-a1a7-fb431aff9280@arm.com \
--to=gdb@sourceware.org \
--cc=Richard.Earnshaw@arm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=carlos@redhat.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jbeulich@suse.com \
--cc=joel@rtems.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=nickc@redhat.com \
--cc=rguenther@suse.de \
--cc=thiago.bauermann@linaro.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