public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bartlomiej Sieka <tur@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix host tool build breakage, take two
Date: Wed, 02 Apr 2008 17:59:48 +0200	[thread overview]
Message-ID: <47F3AD74.4000900@semihalf.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0804020953090.8273@blarg.am.freescale.net>

Kumar Gala wrote:
> On Tue, 1 Apr 2008, Wolfgang Denk wrote:
[...]
>>> Any ideas on how to work around this?  Do we really intend to pick up
>>> the system md5.h or should we be getting the one from u-boot/include/
>>> md5.h?
>> We need the system md5.h, I think. We'll investigate.
> 
> If I force things to use the md5.h in u-boot/include things seem to build.
> Here's the patch for the forcing:

I think that generally it is a better idea to use U-Boot's includes when
building for the host system, as this gives us better control over what
exactly gets included. But then on the other hand, tools/Makefils has this:

CPPFLAGS   = -idirafter $(SRCTREE)/include \
		-idirafter $(OBJTREE)/include2 \
		-idirafter $(OBJTREE)/include \

Could anyone comment on the reasons why we try U-Boot's includes after
system includes? Perhaps it would be a good idea to reverse the order --
see below for a quick RFC patch (compile-tested on two arm and two ppc
boards, each arch with and without CONFIG_FIT enabled).

Kumar - could you try the patch out and see if it helps your build issue?

Regards,
Bartlomiej

diff --git a/tools/Makefile b/tools/Makefile
index 8784a6d..93f74aa 100644
--- a/tools/Makefile
+++ b/tools/Makefile
@@ -117,7 +117,7 @@ BINS        := $(addprefix $(obj),$(BIN_FILES))
  #
  # Use native tools and options
  #
-CPPFLAGS   = -idirafter $(SRCTREE)/include \
+CPPFLAGS   = -I $(SRCTREE)/include \
		-idirafter $(OBJTREE)/include2 \
		-idirafter $(OBJTREE)/include \
		-DTEXT_BASE=$(TEXT_BASE) -DUSE_HOSTCC

  reply	other threads:[~2008-04-02 15:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 14:06 [U-Boot-Users] [PATCH] Fix host tool build breakage, take two Bartlomiej Sieka
2008-03-27 14:44 ` Markus Klotzbücher
2008-03-27 14:44 ` Haavard Skinnemoen
2008-03-28 13:19   ` Kumar Gala
2008-03-28 14:45     ` Wolfgang Denk
2008-03-28 15:44       ` Kumar Gala
2008-03-31 16:50         ` Kumar Gala
2008-03-31 20:23           ` Wolfgang Denk
2008-04-01 15:04             ` Kumar Gala
2008-04-01 20:41               ` Wolfgang Denk
2008-04-02 14:55                 ` Kumar Gala
2008-04-02 15:59                   ` Bartlomiej Sieka [this message]
2008-04-02 17:24                     ` Kumar Gala
2008-04-02 18:57                     ` Wolfgang Denk
2008-04-02 21:19                       ` [U-Boot-Users] [RFC] Rename include/md5.h to u-boot-md5.h Andy Fleming
2008-04-02 21:50                         ` Kumar Gala
2008-04-02 22:06                           ` Andy Fleming
2008-04-03 21:49                         ` Timur Tabi
2008-04-06 11:18                         ` Jean-Christophe PLAGNIOL-VILLARD
2008-04-14  1:09                         ` Wolfgang Denk
2008-04-03 16:33                       ` [U-Boot-Users] [PATCH] Fix host tool build breakage, take two Bartlomiej Sieka
2008-04-03 18:26                         ` Wolfgang Denk
2008-04-03 18:36                           ` Scott Wood
2008-04-03 20:09                             ` Andy Fleming
2008-04-03 22:04                             ` 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=47F3AD74.4000900@semihalf.com \
    --to=tur@semihalf.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