public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Afzal Mohammed <afzal.mohd.ma@gmail.com>
Cc: Clark Williams <williams@redhat.com>,
	rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 1/2] rt-tests: Allow cross compilation
Date: Fri, 23 Aug 2019 17:03:46 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.21.1908231703240.7154@planxty> (raw)
In-Reply-To: <eb3b222b7741d16bf45735f59015c40fcbb31ba2.1566455869.git.afzal.mohd.ma@gmail.com>



On Thu, 22 Aug 2019, Afzal Mohammed wrote:

> $ make CROSS_COMPILE=<my-toolchain-prefix>
> 
> currently does not cause source to be built using the intended
> toolchain, instead will use the host toolchain.
> 
> CC & AR are not updated with CROSS_COMPILE value since they are
> predefined make variables (with default cc & ar respectively) combined
> with the fact that CC & AR variables are updated in the makefile only if
> not already defined due to the usage of '?='.
> 
> Signed-off-by: Afzal Mohammed <afzal.mohd.ma@gmail.com>
> ---
>  Makefile | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Makefile b/Makefile
> index 51b8dea..b573408 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1,6 +1,6 @@
>  VERSION = 1.5
> -CC?=$(CROSS_COMPILE)gcc
> -AR?=$(CROSS_COMPILE)ar
> +CC = $(CROSS_COMPILE)gcc
> +AR = $(CROSS_COMPILE)ar
>  
>  OBJDIR = bld
>  
> -- 
> 2.23.0

Signed-off-by: John Kacur <jkacur@redhat.com>

      parent reply	other threads:[~2019-08-23 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22  6:49 [PATCH 1/2] rt-tests: Allow cross compilation Afzal Mohammed
2019-08-22  6:49 ` [PATCH 2/2] rt-tests: Let git ignore cscope generated files Afzal Mohammed
2019-08-23 15:06   ` John Kacur
2019-08-23 15:03 ` 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.21.1908231703240.7154@planxty \
    --to=jkacur@redhat.com \
    --cc=afzal.mohd.ma@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --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