Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: Tom Tromey <tom@tromey.com>,
	 "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
	 nd	<nd@arm.com>
Subject: Re: [RFC 2/2] Move gdb's xmalloc and friends to new file
Date: Mon, 17 Jun 2019 17:43:00 -0000	[thread overview]
Message-ID: <87a7egkszy.fsf@tromey.com> (raw)
In-Reply-To: <FA1651F0-3805-4466-8246-6439983AF3B9@arm.com> (Alan Hayward's	message of "Mon, 17 Jun 2019 15:44:58 +0000")

>>>>> "Alan" == Alan Hayward <Alan.Hayward@arm.com> writes:

Alan> Looks like this breaks the building of alloc-ipa.o when using Make 3.81
Alan> I’ve tried this on a few different machines.

Thanks.

My first thought is that maybe we should simply declare 3.81
unsupported.  It was apparently released in 2006:

    https://savannah.gnu.org/forum/forum.php?forum_id=4380

... so it is quite ancient.

Is there some compelling reason to keep supporting it?


If there is, I guess I can experiment to try to find a workaround.

thanks,
Tom


  reply	other threads:[~2019-06-17 17:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 21:30 [RFC 0/2] Let's discuss moving gdbserver to top-level Tom Tromey
2019-05-30 21:30 ` [RFC 1/2] Remove linux-waitpid.c debugging code Tom Tromey
2019-06-03 14:57   ` Simon Marchi
2019-06-03 16:32     ` Tom Tromey
2019-06-05  9:32       ` Pedro Alves
2019-05-30 21:30 ` [RFC 2/2] Move gdb's xmalloc and friends to new file Tom Tromey
2019-06-03 15:03   ` Simon Marchi
2019-06-03 16:33     ` Tom Tromey
2019-06-05  9:40   ` Pedro Alves
2019-06-05 22:33     ` Tom Tromey
2019-06-17 15:45   ` Alan Hayward
2019-06-17 17:43     ` Tom Tromey [this message]
2019-06-17 18:37       ` Pedro Alves
2019-06-18  9:31         ` Alan Hayward
2019-07-03 16:18           ` Alan Hayward
2019-07-13 16:04             ` Tom Tromey
2019-07-16 19:47             ` Pedro Alves
2019-06-03 10:24 ` [RFC 0/2] Let's discuss moving gdbserver to top-level Alan Hayward
2019-06-03 14:27 ` Simon Marchi
2019-06-03 16:30   ` Tom Tromey
2019-06-05  9:16 ` Pedro Alves

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=87a7egkszy.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=Alan.Hayward@arm.com \
    --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