From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
gdb-patches@sourceware.org, John Baldwin <jhb@freebsd.org>
Subject: Re: [PATCH 0/4] Makefile improvements and cleanups
Date: Tue, 15 Nov 2016 17:15:00 -0000 [thread overview]
Message-ID: <336d640aa718087f12f82e9cfa95bb1b@polymtl.ca> (raw)
In-Reply-To: <64d5f928-7710-d9a8-3e71-c87d74ef3414@redhat.com>
On 2016-11-15 11:56, Pedro Alves wrote:
> On 11/13/2016 03:26 PM, Simon Marchi wrote:
>> 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.
>
> You mean their ports scripts? Can you provide some url for reference?
Sure:
FreeBSD has "USES = gmake"
https://svnweb.freebsd.org/ports/head/devel/gdb/Makefile?view=co
OpenBSD has "USE_GMAKE = Yes"
http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/ports/devel/gdb/Makefile?rev=1.45&content-type=text/plain
NetBSD has "USE_TOOLS += gmake"
http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/devel/gdb/Makefile
> John, could you comment from the FreeBSD side?
>
>> 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?
>
> I (and others) have argued before about requiring GNU Make. I think
> last was here:
>
> https://sourceware.org/ml/binutils/2014-05/msg00263.html
>
> I think it makes a lot of sense. FWIW, whenever I build GDB on the
> compile
> farm on some non-GNU machine, like FreeBSD, AIX, NetBSD, etc., I've
> always
> used the preinstalled GNU make.
>
> Time to just do it? We'd need a NEWS entry, I suppose.
I'll wait a bit to collect some more feedback, and if the idea seems
accepted I'll do another series for:
- Documenting the GNU make requirement
- Using pattern rules (patches 1 and 2 of this series)
In the mean time I'll prepare a v2 for patches 3 and 4, which don't
depend on GNU make.
Thanks,
Simon
next prev parent reply other threads:[~2016-11-15 17:15 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 1/4] Makefile: Replace old suffix rules with pattern rules 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: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
2016-11-15 16:57 ` Pedro Alves
2016-11-15 17:15 ` Simon Marchi [this message]
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=336d640aa718087f12f82e9cfa95bb1b@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=palves@redhat.com \
--cc=schwab@linux-m68k.org \
/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