Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	binutils@sourceware.org,        gdb-patches@sourceware.org
Subject: Re: Require GNU make to build binutils-gdb
Date: Fri, 18 Nov 2016 10:33:00 -0000	[thread overview]
Message-ID: <80053c28-1a47-8f80-04fb-7bdf76115077@redhat.com> (raw)
In-Reply-To: <144f4f68acf24fc1084b585700c65b63@polymtl.ca>

Hi Simon,

> In gdb/, we are now making use of GNU make-specific features
> (in particular, pattern rules), so we now require building 
> with GNU make.

> For simplicity and consistency, we were wondering if we should 
> adopt the same policy for the whole binutils-gdb tree.

I think that this is a good idea, although maybe it would be 
helpful to take a two stage approach: for one release (of
binutils) issue an error message if a non-GNU make is used,
but allow a configure option to override this.  (In the same 
way that obsolete targets are currently handled).  Then for 
the release after that make GNU make a hard requirement.

That way we give users a chance to give us feedback if they
are using a non-GNU make and they do not have the option of
changing.

Cheers
  Nick



  parent reply	other threads:[~2016-11-18 10:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 19:11 Simon Marchi
2016-11-17 20:06 ` Mike Frysinger
2016-11-17 20:33   ` Simon Marchi
2016-11-17 20:43     ` Paul Smith
2016-11-17 21:14       ` Simon Marchi
2016-11-17 20:39   ` Andreas Schwab
2016-11-18 10:33 ` Nick Clifton [this message]
2016-11-18 13:00   ` Simon Marchi
2016-11-18 17:04     ` Nick Clifton
2016-11-19  3:04       ` 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=80053c28-1a47-8f80-04fb-7bdf76115077@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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