Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Alan Hayward <Alan.Hayward@arm.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [PATCH] Require GNU make 3.82
Date: Tue, 14 Jul 2020 16:30:48 +0200	[thread overview]
Message-ID: <0803f7e7-8564-c079-e1ee-e9fb3497a319@suse.de> (raw)
In-Reply-To: <1298B553-A75A-4D06-9AC4-4F924B045C16@arm.com>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

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.

Thanks,
- Tom

[-- Attachment #2: 0001-gdbserver-Fix-build-with-make-3.81.patch --]
[-- Type: text/x-patch, Size: 802 bytes --]

[gdbserver] Fix build with make 3.81

---
 gdb/gdbserver/Makefile.in | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/gdb/gdbserver/Makefile.in b/gdb/gdbserver/Makefile.in
index 16a9f2fd38..687bee2658 100644
--- a/gdb/gdbserver/Makefile.in
+++ b/gdb/gdbserver/Makefile.in
@@ -580,9 +580,22 @@ ax.o: ax.c
 	$(COMPILE) $(WARN_CFLAGS_NO_FORMAT) $<
 	$(POSTCOMPILE)
 
+ifeq ($(WORKAROUND_ALLOC_IPA),)
+ifeq ($(MAKE_VERSION),3.81)
+WORKAROUND_ALLOC_IPA = 1
+else
+WORKAROUND_ALLOC_IPA = 0
+endif
+endif
+
+ifeq ($(WORKAROUND_ALLOC_IPA),0)
 alloc-ipa.o: ../alloc.c
 	$(IPAGENT_COMPILE) $(WARN_CFLAGS_NO_FORMAT) $<
 	$(POSTCOMPILE)
+else
+alloc-ipa.o: ../alloc.c
+	@$(MAKE) $(FLAGS_TO_PASS) WORKAROUND_ALLOC_IPA=0 alloc-ipa.o
+endif
 
 # Rules for objects that go in the in-process agent.
 

  parent reply	other threads:[~2020-07-14 14:30 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 [this message]
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
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=0803f7e7-8564-c079-e1ee-e9fb3497a319@suse.de \
    --to=tdevries@suse.de \
    --cc=Alan.Hayward@arm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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