From: Tom de Vries <tdevries@suse.de>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, Alan Hayward <Alan.Hayward@arm.com>,
Eli Zaretskii <eliz@gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH] Require GNU make 3.82
Date: Wed, 15 Jul 2020 23:48:00 +0200 [thread overview]
Message-ID: <59ab35a5-6bed-e335-ca78-dedcb8871291@suse.de> (raw)
In-Reply-To: <20200715121436.7c005c10@f32-m1.lan>
On 7/15/20 9:14 PM, Kevin Buettner wrote:
> On Wed, 15 Jul 2020 19:31:44 +0200
> Tom de Vries <tdevries@suse.de> wrote:
>
>> On 7/15/20 7:14 PM, Kevin Buettner wrote:
>>> On Wed, 15 Jul 2020 09:46:58 +0200
>>> Tom de Vries <tdevries@suse.de> wrote:
>>>
>>>> On 7/14/20 4:30 PM, Tom de Vries wrote:
>>>>> On 7/18/19 12:57 PM, Alan Hayward wrote:
>>>>>>
>>>>>>
>>>>>>> On 18 Jul 2019, at 07:17, Eli Zaretskii <eliz@gnu.org> wrote:
>>>>>>>
>>>>>>>> From: Alan Hayward <Alan.Hayward@arm.com>
>>>>>>>> CC: nd <nd@arm.com>, Alan Hayward <Alan.Hayward@arm.com>
>>>>>>>> Date: Mon, 15 Jul 2019 10:11:29 +0000
>>>>>>>>
>>>>>>>> Gdbserver has failed to build with GNU make 3.81 since commit 08f10e02be.
>>>>>>>
>>>>>>> Which feature of Make 3.82 and later is required to successfully
>>>>>>> build gdbserver?
>>>>>>>
>>>>>>
>>>>>> It’s not a specific feature in 3.82 that is required.
>>>>>>
>>>>>> It looks like it is a bug in 3.81. The GDB makefile isn’t doing anything special
>>>>>> and everything works using 3.82 upwards.
>>>>>>
>>>>>> Rewriting the makefile to work around the issue is probably going to be a little
>>>>>> messy.
>>>>>>
>>>>>
>>>>> This patch (on top of gdb 9.1) works around the issue for make 3.81.
>>>>>
>>>>> Build with make 3.81 and make 4.2.1 on x86_64-linux.
>>>>
>>>> And here (
>>>> https://sourceware.org/pipermail/gdb-patches/2019-December/163800.html )
>>>> is a patch (with a detailed analysis of the actual failure) on master
>>>> that fixes the build with 3.81.
>>>
>>> So Bernd's patch should be backported to 9.1?
>>
>> Um, we've already released 9.2, and I presume closed the branch? So I'm
>> not sure what you mean.
>
> Back on the July 14, you posted a patch relative to gdb 9.1 which works around the make 3.81 issue. But it seems that Bernd also has a patch from late last year which fixes that issue. (It appears to me that Bernd's patch is on the trunk, but I haven't checked to see what branches Bernd's patch might be on.)
>
> Is Bernd's patch insufficient to fix the 3.81 issues that you're seeing?
I've just tested it, and it's sufficient.
The reason why I posted that patch, is because I was not aware of
Bernd's patch.
Thanks,
- Tom
next prev parent reply other threads:[~2020-07-15 21:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 10:11 Alan Hayward
2019-07-16 0:51 ` Kevin Buettner
2019-07-16 10:36 ` Alan Hayward
2019-07-18 6:17 ` Eli Zaretskii
2019-07-18 10:00 ` Eli Zaretskii
2019-07-18 10:57 ` Alan Hayward
2019-08-01 16:09 ` Alan Hayward
2020-07-14 14:30 ` Tom de Vries
2020-07-15 7:46 ` Tom de Vries
2020-07-15 17:14 ` Kevin Buettner
2020-07-15 17:31 ` Tom de Vries
2020-07-15 19:14 ` Kevin Buettner
2020-07-15 21:48 ` Tom de Vries [this message]
2020-07-14 11:47 ` 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=59ab35a5-6bed-e335-ca78-dedcb8871291@suse.de \
--to=tdevries@suse.de \
--cc=Alan.Hayward@arm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=nd@arm.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).