From: John Kacur <jkacur@redhat.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: williams@redhat.com, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] Makefile: Set CC/AR variable only if it doesn't have a value
Date: Tue, 5 Jan 2016 23:59:27 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.20.1601052356510.1732@riemann> (raw)
In-Reply-To: <1451847271-31571-1-git-send-email-raj.khem@gmail.com>
On Sun, 3 Jan 2016, Khem Raj wrote:
> This helps it compile with clang or any other compilers besides gcc
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 1e4b7d1..2c2d396 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1,6 +1,6 @@
> VERSION = 0.96
> -CC=$(CROSS_COMPILE)gcc
> -AR=$(CROSS_COMPILE)ar
> +CC?=$(CROSS_COMPILE)gcc
> +AR?=$(CROSS_COMPILE)ar
>
> OBJDIR = bld
>
> --
Signed-off-by: John Kacur <jkacur@gmail.com>
I added this to the next build.
Note, I read everything in the thread, and I think there was a bit of
confusion over thinking this was a kernel Makefile and not
the rt-tests one. As clark said, this is indeed the appropriate place to
discuss user space tools that are to do with real-time.
Perhaps after [PATCH] add rt-tests: to make it clear.
This patch is fine, it changes nothing other than letting the Khem and
others specify CC and AR from the command line when typing make.
Thanks
prev parent reply other threads:[~2016-01-05 22:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 18:54 [PATCH] Makefile: Set CC/AR variable only if it doesn't have a value Khem Raj
2016-01-04 13:39 ` Jeff Epler
2016-01-04 14:40 ` Clark Williams
2016-01-05 3:12 ` Jeff Epler
2016-01-04 16:20 ` Khem Raj
2016-01-04 16:25 ` Uwe Kleine-König
2016-01-05 21:15 ` Henrik Austad
2016-01-05 21:20 ` Khem Raj
2016-01-05 21:42 ` Uwe Kleine-König
2016-01-04 19:21 ` Arnout Vandecappelle
2016-01-04 23:13 ` Khem Raj
2016-01-05 22:59 ` John Kacur [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=alpine.LFD.2.20.1601052356510.1732@riemann \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=raj.khem@gmail.com \
--cc=williams@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;
as well as URLs for NNTP newsgroup(s).