This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH] update automake version to 1.11.6
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: GDB <gdb-patches at sourceware dot org>, Binutils <binutils at sourceware dot org>, Doug Evans <dje at google dot com>
- Date: Mon, 23 Mar 2015 05:57:20 -0700
- Subject: Re: [PATCH] update automake version to 1.11.6
- Authentication-results: sourceware.org; auth=none
- References: <20150311094134 dot GE9455 at vapier> <1426310999-13103-1-git-send-email-vapier at gentoo dot org> <20150319120631 dot GB4884 at adacore dot com> <CADPb22SsgzcWz3XhQ_KgezXsV2Y190711fdo+oHK6fuWk=X3sw at mail dot gmail dot com> <20150319230427 dot GI4128 at vapier> <CADPb22QuAXWT33hf1QdJfzHFuK46mZ=y=4vm-CG1rptZsN4JwA at mail dot gmail dot com> <20150321195953 dot GA24181 at vapier> <CAKOQZ8y8aYVM0ncJVfEYBcy1vEUaqLJ+C1un3vC51bpbr=wEfQ at mail dot gmail dot com> <20150323124600 dot GC5438 at adacore dot com>
On Mon, Mar 23, 2015 at 5:46 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> > i don't have a problem with requiring people to use the same exact
>> version.
>> > i do think that requiring them to build/install by hand is
>> > unreasonable. it's pretty rare (by design) for projects to do this
>> > sort of thing (commit the generated autotools), so it's pretty rare
>> > for this to be an issue, so it's pretty rare for people to be
>> > required to manage this. it's a throw back to pre-distro days when
>> > people were used to building/install software themselves, and it's
>> > unnecessary friction for new people to get into the development
>> > process today. death by a thousand cuts and all that.
>>
>> It's only a barrier for people who need to change the configure.ac or
>> Makefile.am files, which is not most developers.
>
> Agreed.
>
> Also, I don't think that building autoconf and automake once every
> few years, and then using that to generate the files is really that
> much of a barrier. In the meantime, it allows us to avoid the noise
> you get when slightly different versions generate slightly different
> code. I personally do verify the changes in the configure files,
> for instance, and ask myself whether each hunk I see makes sense
> to me or not. Seeing unrelated changes because others used a different
> version makes that process a little harder (and, most of the time,
> I'll just start over, and push a patch that first regenerates the
> file).
We should coordinate this with GCC. I have been using autoconf
and automake specified in
https://gcc.gnu.org/install/prerequisites.html
--
H.J.