Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: Require GNU make to build binutils-gdb
Date: Sat, 19 Nov 2016 03:04:00 -0000	[thread overview]
Message-ID: <fff125563880fa7dd26688ca4d21b301@polymtl.ca> (raw)
In-Reply-To: <5fab6734-6b06-fc27-785f-cb3af2076d4e@redhat.com>

On 2016-11-18 12:04, Nick Clifton wrote:
> Well, the top-level Makefile is shared with gcc, so we would have
> to get approval there as well.  Putting the check in the binutils/
> Makefile would certainly be easier, and it should be sufficient
> (The only target that I could find that does not build the binutils
> sub-directory is the v810, which is not supported as a binutils
> target anyway).

Hi Nick,

I tried to prototype putting a check in binutils/Makefile.am, but my 
automake knowledge did not get me very far.  Being one level of 
abstraction above make, it doesn't seem possible at first sight to use 
something like

   ifdef .FEATURES
   $(error "defined")
   else
   $(error "not defined")
   endif

Any idea how to proceed?

Simon


      reply	other threads:[~2016-11-19  3:04 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
2016-11-18 13:00   ` Simon Marchi
2016-11-18 17:04     ` Nick Clifton
2016-11-19  3:04       ` Simon Marchi [this message]

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=fff125563880fa7dd26688ca4d21b301@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.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