public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>,
	Bernd Edlinger <bernd.edlinger@hotmail.de>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Alan Hayward <Alan.Hayward@arm.com>,
	Kevin Buettner <kevinb@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] Fix build with GNU Make 3.81
Date: Wed, 15 Jul 2020 10:19:28 +0200	[thread overview]
Message-ID: <05bc8ac7-816d-5bc4-b3ed-80580341053d@suse.de> (raw)
In-Reply-To: <ecd4e216-c528-cf05-6a5a-e41ae0c0d79a@simark.ca>

On 12/14/19 7:21 PM, Simon Marchi wrote:
> On 2019-12-14 3:15 a.m., Bernd Edlinger wrote:
>> Hi,
>>
>> I have a minor problem with building the gdbserver, alloc-ipa.o
>> on ubuntu 14.04 which still uses GNU Make 3.81.
>>
>> Since several quirks for this GNU Make version exist, I suppose
>> this version is still intended to be supported.
>>
>> This patch fixes the build with this make version, and works
>> also for newer versions.
>>
>>
>> Thanks
>> Bernd.
>>
> 
> Hi Bernd,
> 
> The intention was to support make >= 3.82, since this commit:
> 
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c6bdbeb7c468489da9468445057d245929c3d91c
> 
> Though it's possible that (stale) references and tweaks for make 3.81
> are left.
> 
> I don't mind if we merge simple fixes like that, as long as it doesn't compromise
> building with newer versions.  Like, if there was a super-duper cool feature of
> make 3.82 that would really simplify our lives, we would still prefer using that
> over keeping compatibility with make 3.81.

I don't follow this reasoning.

There's a bug in make 3.81, which we run into with the gdb build.

We then require make 3.82, such that gdb builds again for all supported
make versions.

Subsequently (that is, 3 days later) we work around the bug in make 3.81
with a gdb commit.

But we decide to still require make 3.82, even if the original reason to
do so is no longer valid, and I'm assuming we haven't started using make
3.82 features in the 3 days inbetween.

Are there other considerations at play here, that are not being made
explicit?

Because if there are not, we should update NEWS to say we support 3.81
again.

Thanks,
- Tom

  parent reply	other threads:[~2020-07-15  8:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14  8:15 Bernd Edlinger
2019-12-14 18:21 ` Simon Marchi
2019-12-19 17:29   ` Tom Tromey
2019-12-23  7:30     ` Joel Brobecker
2020-07-15  8:19   ` Tom de Vries [this message]
2020-07-15 13:44     ` Simon Marchi
2020-07-15 18:30       ` Tom de Vries

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=05bc8ac7-816d-5bc4-b3ed-80580341053d@suse.de \
    --to=tdevries@suse.de \
    --cc=Alan.Hayward@arm.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=simark@simark.ca \
    --cc=tom@tromey.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).