From: Richard Earnshaw <rearnsha@arm.com>
To: Ralf Corsepius <ralf.corsepius@rtems.org>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Require GNU make?
Date: Thu, 29 May 2014 13:23:00 -0000 [thread overview]
Message-ID: <538734C8.4030300@arm.com> (raw)
In-Reply-To: <538730C1.6040105@rtems.org>
On 29/05/14 14:06, Ralf Corsepius wrote:
> On 05/29/2014 02:54 PM, Richard Earnshaw wrote:
>
>> Not directly relevant, but I put a feature into the newlib build earlier
>> this year that relied on a GNU make extension. There were no objections
>> at the time I did that.
> Correct me if I'm wrong, but IIRC, GCC already requires gmake.
> As newlib is commonly used with GCC, probably everybody who uses newlib
> also uses gmake :-)
>
> Ralf
>
>
Possibly. As I said, it's not directly relevant...
I tend to build all off gcc/binutils/gdb/newlib in one go, so always use
gmake for the lot.
R.
next prev parent reply other threads:[~2014-05-29 13:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 22:48 [RFA:] fix PR ld/16963, missing SEARCH_DIR for non-sysroot cross-builds Hans-Peter Nilsson
2014-05-20 9:21 ` Alan Modra
2014-05-20 11:23 ` Hans-Peter Nilsson
2014-05-20 12:36 ` Alan Modra
2014-05-20 16:20 ` Hans-Peter Nilsson
2014-05-22 8:02 ` Alan Modra
2014-05-28 13:16 ` Hans-Peter Nilsson
2014-05-28 14:15 ` Alan Modra
2014-05-29 10:08 ` Require GNU make? (was: Re: [RFA:] fix PR ld/16963, missing SEARCH_DIR for non-sysroot cross-builds) Pedro Alves
2014-05-29 12:54 ` Require GNU make? Richard Earnshaw
2014-05-29 13:09 ` Ralf Corsepius
2014-05-29 13:23 ` Richard Earnshaw [this message]
2014-05-29 16:09 ` ISHIKAWA,chiaki
2014-05-29 22:17 ` Pedro Alves
2014-05-29 22:23 ` Joel Brobecker
2014-05-29 15:32 ` Jeff Law
2014-06-04 18:33 ` Tom Tromey
2014-06-02 6:30 ` [RFA:] fix PR ld/16963, missing SEARCH_DIR for non-sysroot cross-builds Alan Modra
2014-06-02 17:28 ` Hans-Peter Nilsson
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=538734C8.4030300@arm.com \
--to=rearnsha@arm.com \
--cc=binutils@sourceware.org \
--cc=ralf.corsepius@rtems.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).