public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] tools: Use override when changing CC, 	CFLAGS , etc.
Date: Tue, 20 Oct 2009 21:17:43 -0400	[thread overview]
Message-ID: <200910202117.44325.vapier@gentoo.org> (raw)
In-Reply-To: <4ADE3176.7000508@freescale.com>

On Tuesday 20 October 2009 17:53:58 Scott Wood wrote:
> 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).
> 
> I was looking at making static pattern rules to divert host objects to a
> host rule, with separate object lists for files that want pedantic and
> non-pedantic (leaving the current set of individual file rules would
> cause conflicts).
> 
> It seems that nothing in tools/Makefile is using -pedantic or any of the
> other HOSTCFLAGS set in tools/Makefile; HOSTCFLAGS is getting
> overwritten by config.mk.  It looks like maybe this was introduced when
> HOST_CFLAGS was changed to HOSTCFLAGS.
> 
> Any thoughts on how to untangle things?  What flags to we really want to
> use here?  Given the number of files that have been exempted, do we
> still want to keep the -pedantic stuff around?

i dislike -pedantic/-ansi (i find it a waste of time), but i think Wolfgang 
wants to support older crap

having all hostflags be in the top level would be good at any rate rather than 
duplicating into tools/ ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20091020/319e2bf5/attachment.pgp 

  reply	other threads:[~2009-10-21  1:17 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
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     ` Mike Frysinger [this message]
2009-10-19 22:35 ` 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=200910202117.44325.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox