From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] denx/master is not building for OMAP3 platforms except Beagle
Date: Mon, 04 Oct 2010 14:56:39 +0200 [thread overview]
Message-ID: <4CA9CF07.3010409@denx.de> (raw)
In-Reply-To: <m2hbh2ruux.fsf@ohwell.denx.de>
Hello Detlev,
Detlev Zundel wrote:
> Hi Heiko,
>
> [...]
>
>>> Surely having e.g.
>>>
>>> #if (not fixed config)
>>> #error See http://blah/blah/blah for information about how to fix your board
>>> #endif
>>>
>>> would be more beneficial than an obscure compiler failure that doesn't
>>> even reference useful keywords?
>> but that would result in editing *all* config files, which are not
>> coverted.
>
> Are you sure? Isn't there some central place in arm land where board.h
> is included? Such an ifdef there would catch all configs or what am I
> missing?
How would you detect there, if the config file (board.h) is converted
for relocation and working or not? This help should only be printed
if CONFIG_SYS_ARM_WITHOUT_RELOC is not defined and compiling fails ...
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2010-10-04 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 10:50 [U-Boot] denx/master is not building for OMAP3 platforms except Beagle Hiremath, Vaibhav
2010-10-03 11:06 ` Albert ARIBAUD
2010-10-03 13:46 ` Hiremath, Vaibhav
2010-10-03 18:37 ` Wolfgang Denk
2010-10-04 5:08 ` Hiremath, Vaibhav
2010-10-04 6:00 ` Heiko Schocher
2010-10-04 6:40 ` Rogan Dawes
2010-10-04 8:06 ` Heiko Schocher
2010-10-04 12:43 ` Detlev Zundel
2010-10-04 12:50 ` Wolfgang Denk
2010-10-04 12:56 ` Heiko Schocher [this message]
2010-10-05 11:46 ` Detlev Zundel
2010-10-05 12:34 ` Bas Mevissen
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=4CA9CF07.3010409@denx.de \
--to=hs@denx.de \
--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.