From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Sandbox question
Date: Thu, 01 Dec 2011 17:35:14 +0100 [thread overview]
Message-ID: <4ED7ACC2.6060209@gmail.com> (raw)
Dear Simon,
I started to play around with new sandbox architecture and encountered a
serious problem.
Due to the '-nostdinc' switch the file arch/sandbox/cpu/os.c requires
additional CPPFLAGS '-I/usr/include'. On my debian box this is not
enough since the bits/*.h are placed in /usr/include/i386-linux-gnu and
therefore I get errors when compiling arch/sandbox/os.c.
Are there any clean solution to get this working?
best regards
Andreas Bie?mann
next reply other threads:[~2011-12-01 16:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 16:35 Andreas Bießmann [this message]
2011-12-01 18:13 ` [U-Boot] Sandbox question Simon Glass
2011-12-01 19:21 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2012-04-23 6:41 Wolfgang Denk
2012-04-23 15:41 ` Mike Frysinger
2012-04-23 17:32 ` Matthias Weisser
2012-04-23 17:39 ` Wolfgang Denk
2012-04-23 17:49 ` Matthias Weisser
2012-04-23 18:30 ` Wolfgang Denk
2012-04-24 9:25 ` Matthias Weißer
2012-04-23 17:58 ` Simon Glass
2012-04-23 18:39 ` Wolfgang Denk
2012-04-23 18:54 ` Mike Frysinger
2012-04-23 19:03 ` Mike Frysinger
2012-04-23 19:33 ` Wolfgang Denk
2012-04-23 20:57 ` Mike Frysinger
2012-04-23 21:16 ` Mike Frysinger
2012-04-23 21:17 ` Wolfgang Denk
2012-04-23 21:32 ` Mike Frysinger
2013-12-06 23:36 [U-Boot] [PATCH 0/8] Secure boot improvements and test on Beaglebone Black Simon Glass
2013-12-30 7:40 ` [U-Boot] sandbox question TigerLiu at viatech.com.cn
2013-12-31 0:42 ` TigerLiu at viatech.com.cn
2014-01-07 23:58 ` Simon Glass
2014-01-08 0:52 ` TigerLiu at viatech.com.cn
2014-01-08 3:46 ` Abraham Varricatt
2014-01-08 10:30 ` TigerLiu at viatech.com.cn
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=4ED7ACC2.6060209@gmail.com \
--to=andreas.devel@googlemail.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