From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: schwab@linux-m68k.org, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Makefile improvements and cleanups
Date: Sun, 13 Nov 2016 16:25:00 -0000 [thread overview]
Message-ID: <837f87cpnz.fsf@gnu.org> (raw)
In-Reply-To: <968dffb716723c39a8a3cf0ab2d5bfca@polymtl.ca> (message from Simon Marchi on Sun, 13 Nov 2016 10:26:16 -0500)
> Date: Sun, 13 Nov 2016 10:26:16 -0500
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Cc: gdb-patches@sourceware.org
>
> As an honest follow-up question: do we need to stay compatible with
> other makes than GNU make? From what I can see, Open/Net/FreeBSD all
> use gmake to build their port of GDB already. I don't know about other
> OSes on which people build GDB on (Windows, OS X, Solaris?). If GNU
> make is readily available on these, perhaps we can consider making it a
> requirement?
The MS-Windows builds of GDB use GNU Make.
next prev parent reply other threads:[~2016-11-13 16:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 3:46 Simon Marchi
2016-11-13 3:46 ` [PATCH 3/4] Makefile: Flatten and sort file lists Simon Marchi
2016-11-15 16:46 ` Pedro Alves
2016-11-13 3:46 ` [PATCH 2/4] Makefile: Replace explicit subdir rules with pattern rules Simon Marchi
2016-11-15 17:54 ` Pedro Alves
2016-11-15 18:00 ` Simon Marchi
2016-11-15 18:36 ` Pedro Alves
2016-11-15 18:41 ` Simon Marchi
2016-11-13 3:46 ` [PATCH 1/4] Makefile: Replace old suffix " Simon Marchi
2016-11-13 3:56 ` [PATCH 0/4] Makefile improvements and cleanups Simon Marchi
2016-11-13 8:49 ` Andreas Schwab
2016-11-13 15:26 ` Simon Marchi
2016-11-13 16:25 ` Eli Zaretskii [this message]
2016-11-15 16:57 ` Pedro Alves
2016-11-15 17:15 ` Simon Marchi
2016-11-15 17:51 ` Pedro Alves
2016-11-15 21:58 ` Pedro Alves
2016-11-15 22:10 ` Simon Marchi
2016-11-15 21:46 ` John Baldwin
2016-11-17 18:54 ` John Baldwin
2016-11-17 19:20 ` Simon Marchi
2016-11-17 22:36 ` John Baldwin
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=837f87cpnz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.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