This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC 2/2] Move gdb's xmalloc and friends to new file
- From: Pedro Alves <palves at redhat dot com>
- To: Tom Tromey <tom at tromey dot com>, Alan Hayward <Alan dot Hayward at arm dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, nd <nd at arm dot com>
- Date: Mon, 17 Jun 2019 19:37:39 +0100
- Subject: Re: [RFC 2/2] Move gdb's xmalloc and friends to new file
- References: <20190530213046.20542-1-tom@tromey.com> <20190530213046.20542-3-tom@tromey.com> <FA1651F0-3805-4466-8246-6439983AF3B9@arm.com> <87a7egkszy.fsf@tromey.com>
On 6/17/19 6:43 PM, Tom Tromey wrote:
>>>>>> "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?
>
I think it depends more on what distributions ship than what
the release date was. E.g., if you look around the last couple
stable releases of popular stable distros (e.g., ubuntu, debian, fedora),
which GNU Make version did they ship? If the GNU Make version shipped
by default is not 4.x, is there an easy optional rpm/deb package
for GNU Make 4.x available?
This was the same kind of investigation that led to the GCC 4.8
minimum requirement.
Also, looking around the GCC compile farm machine (including the
/opt/ dirs) for what is available may be a good hint/proxy for
determining whether bumping the requirement could cause trouble
for people.
> If there is, I guess I can experiment to try to find a workaround.
Thanks,
Pedro Alves