All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] tools: Use override when changing CC, CFLAGS, etc.
Date: Mon, 19 Oct 2009 16:56:37 -0500	[thread overview]
Message-ID: <4ADCE095.1090301@freescale.com> (raw)
In-Reply-To: <200910191742.53914.vapier@gentoo.org>

Mike Frysinger wrote:
> On Monday 19 October 2009 17:24:35 Scott Wood wrote:
>> If the user has specified a CC or similar on the command line, that is the
>> cross compiler, not the host compiler.  Override is needed to keep these
>> assignments from being ignored in that case.
> 
> then again, if we didnt mix host and target variable names, this wouldnt be a 
> problem.  in a sane world, all of the host stuff would be HOSTXX (or BUILDXX).

Right... I initially tried substituting in HOSTCC, but it still tried to 
use CC, probably from an implicit rule that would need to be made 
explicit in order to use HOSTCC.

I can try to respin it with a new explicit rule if y'all want.

-Scott

  reply	other threads:[~2009-10-19 21:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 21:24 [U-Boot] [PATCH 2/2] tools: Use override when changing CC, CFLAGS, etc Scott Wood
2009-10-19 21:42 ` Mike Frysinger
2009-10-19 21:56   ` Scott Wood [this message]
2009-10-19 22:37     ` [U-Boot] [PATCH 2/2] tools: Use override when changing CC, CFLAGS , etc Mike Frysinger
2009-10-20 21:53   ` [U-Boot] [PATCH 2/2] tools: Use override when changing CC, CFLAGS, etc Scott Wood
2009-10-21  1:17     ` [U-Boot] [PATCH 2/2] tools: Use override when changing CC, CFLAGS , etc Mike Frysinger
2009-10-19 22:35 ` [U-Boot] [PATCH 2/2] tools: Use override when changing CC, CFLAGS, etc Wolfgang Denk

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=4ADCE095.1090301@freescale.com \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.