public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] problem building next on P2020DS_36BIT
Date: Thu, 10 Dec 2009 14:35:03 -0600	[thread overview]
Message-ID: <4B215B77.3080906@freescale.com> (raw)
In-Reply-To: <3ED82CB0-0654-41CA-BCA9-8B9AB75F6429@kernel.crashing.org>

Kumar Gala wrote:
> Scott,
> 
> This appears to be related to .depend generation and the patch that seems to cause the issue is:
> 
> Author: Scott Wood <scottwood@freescale.com>
> Date:   Wed Nov 4 18:41:41 2009 -0600
> 
>     makefiles: fixes for building build tools
>     
>     Currently, some of the tools instead set CC to be HOSTCC in order to re-use
>     some pattern rules -- but this fails when the user overrides CC on the make
>     command line.  Also, the HOSTCFLAGS in tools/Makefile are currently not
>     being used because config.mk overwrites them.
> 
> It looks like for some reason we aren't getting the EXTRA_CFLAGS in drivers/bios_emulator/Makefile aren't getting picked up in the .depend generation.

EXTRA_CFLAGS is not part of the u-boot build system.  CFLAGS is, but it 
is not used in dependency generation.

Prior to that change, HOSTCFLAGS was being used inappropriately in 
generating target dependencies.  If you change the HOSTCFLAGS reference 
in drivers/bios_emulator/Makefile to CPPFLAGS, it works.

Unfortunately, that makefile still has to update CFLAGS as well, because 
it's too late at that point for changes to CPPFLAGS to propagate to CFLAGS.

-Scott

      reply	other threads:[~2009-12-10 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 19:22 [U-Boot] problem building next on P2020DS_36BIT Kumar Gala
2009-12-10 19:39 ` Kumar Gala
2009-12-10 20:35   ` Scott Wood [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=4B215B77.3080906@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox