From: Pedro Alves <palves@redhat.com>
To: Jonas Maebe <jonas-devlists@watlock.be>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] Document new hard requirement on GNU make
Date: Thu, 17 Nov 2016 12:43:00 -0000 [thread overview]
Message-ID: <adfcbd15-6711-bd24-59f8-5fcd4e8e74b5@redhat.com> (raw)
In-Reply-To: <20161117110550.Horde.w92Gcy2wqn5YLYD_XFx1epA@mail.elis.ugent.be>
On 11/17/2016 10:05 AM, Jonas Maebe wrote:
>
> Eli Zaretskii wrote on Thu, 17 Nov 2016:
>
>>> Date: Wed, 16 Nov 2016 17:04:59 -0500
>>> From: Simon Marchi <simon.marchi@polymtl.ca>
>>> Cc: gdb-patches@sourceware.org
>>>
>>> So I'm back at having no idea what version we should require.
>>
>> I guess that'd be 3.81, then.
>
> (Mac) OS X/macOS also ships with 3.81. Although that one will presumably
> never be updated to anything newer due to the switch to GPLv3, so it may
> not make sense to limit yourself based on that.
I believe https://www.macports.org/ should make it easy to install
whatever newer dependency than what ships built in with the OS.
(I don't use MacOS, though.) According to:
https://trac.macports.org/browser/trunk/dports/devel/gmake/Portfile
they have 4.1 available.
So I think macOS wouldn't be a problem if we wanted to require
something newer.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-11-17 12:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 16:11 [PATCH 0/4] Require " Simon Marchi
2016-11-16 16:10 ` [PATCH 4/4] Makefile: Replace explicit subdir rules with pattern rules Simon Marchi
2016-11-16 17:11 ` Pedro Alves
2016-11-16 16:12 ` [PATCH 2/4] Remove code that checks for GNU/non-GNU make Simon Marchi
2016-11-16 16:32 ` Eli Zaretskii
2016-11-16 16:39 ` Andreas Schwab
2016-11-16 17:12 ` Pedro Alves
2016-11-16 17:12 ` Simon Marchi
2016-11-16 17:09 ` Pedro Alves
2016-11-16 16:12 ` [PATCH 1/4] Document new hard requirement on GNU make Simon Marchi
2016-11-16 16:29 ` Eli Zaretskii
2016-11-16 17:05 ` Simon Marchi
2016-11-16 17:23 ` Eli Zaretskii
2016-11-16 22:05 ` Simon Marchi
2016-11-16 23:34 ` Pedro Alves
2016-11-17 12:39 ` Pedro Alves
2016-11-17 13:39 ` Simon Marchi
2016-11-17 16:10 ` Eli Zaretskii
2016-11-17 3:35 ` Eli Zaretskii
2016-11-17 10:06 ` Jonas Maebe
2016-11-17 12:43 ` Pedro Alves [this message]
2016-11-16 16:12 ` [PATCH 3/4] Makefile: Replace old suffix rules with pattern rules Simon Marchi
2016-11-16 16:35 ` Eli Zaretskii
2016-11-16 16:56 ` Pedro Alves
2016-11-16 17:14 ` Eli Zaretskii
2016-11-16 17:32 ` Pedro Alves
2016-11-16 17:49 ` Eli Zaretskii
2016-11-16 17:58 ` Pedro Alves
2016-11-16 19:38 ` Simon Marchi
2016-11-16 19:58 ` Pedro Alves
2016-11-16 20:18 ` Simon Marchi
2016-11-16 19:11 ` Pedro Alves
2016-11-17 16:52 ` Simon Marchi
2016-11-17 16:57 ` Pedro Alves
2016-11-17 17:05 ` [PATCH 0/4] Require GNU make Simon Marchi
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=adfcbd15-6711-bd24-59f8-5fcd4e8e74b5@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jonas-devlists@watlock.be \
/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