Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: Pedro Alves <palves@redhat.com>, Tom Tromey <tom@tromey.com>
Cc: "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: Wed, 03 Jul 2019 16:18:00 -0000	[thread overview]
Message-ID: <5B7E81C9-C5FC-47AA-AFE9-61031E9C276A@arm.com> (raw)
In-Reply-To: <43591E27-A08D-4138-BB6E-C09BFEA03524@arm.com>



> On 18 Jun 2019, at 10:30, Alan Hayward <Alan.Hayward@arm.com> wrote:
> 
> 
> 
>> On 17 Jun 2019, at 19:37, Pedro Alves <palves@redhat.com> wrote:
>> 
>> 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.
> 
> 
> Glibc requires 4.0:
> https://www.sourceware.org/ml/libc-alpha/2018-08/msg00003.html
> 	Changes to build and runtime requirements:
>  	GNU make 4.0 or later is now required to build glibc.
> 
> 
> GCC still allows 3.8:
> https://gcc.gnu.org/install/prerequisites.html
> 	GNU make version 3.80 (or later)
> 

I’ve done a little more digging into as many machines as I could find:

Ubuntu 16.04, 18.04 - make 4.1
Ubuntu 14.04 - make 4.0
Fedora 27 - make 4.2.1
Redhat 7.5, Centos 7.5, Centos 6 - make 3.82
Redhat 5.8, 6.9 - make 3.81
OpenSuse 42.2 - 4.2.1

Also: https://software.opensuse.org/package/make confirms a mix of 4.21 and
3.82 as the versions in various latest distros.

I’ve tried building using make 3.82, and it works for me.
Make 3.82 was released in 2010.

Any objection upping the minimum make version to 3.82 ?

If so I can raise a patch to add a statement to the NEWS file (similar to
the one that already exists).


Alan.





  reply	other threads:[~2019-07-03 16:18 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 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
2019-06-17 18:37       ` Pedro Alves
2019-06-18  9:31         ` Alan Hayward
2019-07-03 16:18           ` Alan Hayward [this message]
2019-07-13 16:04             ` Tom Tromey
2019-07-16 19:47             ` Pedro Alves
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-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=5B7E81C9-C5FC-47AA-AFE9-61031E9C276A@arm.com \
    --to=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=palves@redhat.com \
    --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