From: Jeroen Hofstee <dasuboot@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] idirafter causes host sha256.h to be included
Date: Sat, 24 May 2014 23:09:39 +0200 [thread overview]
Message-ID: <1400965779.1984.31.camel@yellow> (raw)
In-Reply-To: <CAPnjgZ0seOsF_=mEAph-VN5KTyY2To+WcJLfmviCgsA8b_A6Nw@mail.gmail.com>
Hello Simon,
On vr, 2014-05-23 at 15:37 -1000, Simon Glass wrote:
> On 9 May 2014 12:31, Jeroen Hofstee <dasuboot@myspectrum.nl> wrote:
> > Hello,
> >
> > tools/Makefile uses the following substitution
> >
> > HOST_EXTRACFLAGS += -include $(srctree)/include/libfdt_env.h \
> > $(patsubst -I%,-idirafter%, $(UBOOTINCLUDE)) \
> > ...
> >
> > Which adds -idirafterinclude when compiling image-fit.c. Since
> > mentioned file includes sha256.h, which is a system include on FreeBSD,
> > the system version is included instead of the intended U-boot
> > include/sha256.h and building fails. Without the substitution it builds
> > successfully.
> >
> > What is the intention of using idirafter?
>
> I believe this is so that U-Boot headers are available when building.
> You might need to add a work-around like we have for libfdt_env.h. It
> is also possible that there is a more general solution, sorry I'm not
> sure what it might be.
>
Thanks for mentioning the libfdt_env.h. As mentioned in the thread
discussing the patch errno.h is one of the reasons to require the
dirafter, since the tools need the host version of it. A possible
solution could perhaps be to place such standard headers in a separate
directory and only include it for an u-boot build. The tools can then be
compiled without the idirafter and not including this location as an
include path.
Regards,
Jeroen
next prev parent reply other threads:[~2014-05-24 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 22:31 [U-Boot] idirafter causes host sha256.h to be included Jeroen Hofstee
2014-05-24 1:37 ` Simon Glass
2014-05-24 21:09 ` Jeroen Hofstee [this message]
2014-05-27 3:37 ` Simon Glass
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=1400965779.1984.31.camel@yellow \
--to=dasuboot@myspectrum.nl \
--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.