public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 10:06:15 +0200	[thread overview]
Message-ID: <4CA98AF7.9080309@denx.de> (raw)
In-Reply-To: <4CA976E4.4020104@dawes.za.net>

Hello Rogan,

Rogan Dawes wrote:
> On 2010/10/04 8:00 AM, Heiko Schocher wrote:
>> Hello Hiremath,
>>
>> Hiremath, Vaibhav wrote:
>>> Hi All,
>>>
>>> I think the current denx/matser is broken and is not building up for OMAP3 platforms except Beagle board.
>> but they should compile if you define CONFIG_SYS_ARM_WITHOUT_RELOC
>>
>> or compile with:
>>
>> "CONFIG_SYS_ARM_WITHOUT_RELOC=1 ./MAKEALL board"
>>
>> But be aware, this option wil be removed ...
>>
>> bye,
>> Heiko
> 
> For what it is worth, would it be possible to have a more verbose error
> message that actually provides a reference to what needs to be done,
> rather than simply failing with an obscure message about DRAM configuration?
> 
> I ended up bisecting the tree to find the commit, and suitable
> references for what needs to be done to get a board working again, after
> searching "git log -p" for "SDRAM" got me nowhere.
> 
> 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.

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2010-10-04  8:06 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 [this message]
2010-10-04 12:43       ` Detlev Zundel
2010-10-04 12:50         ` Wolfgang Denk
2010-10-04 12:56         ` Heiko Schocher
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=4CA98AF7.9080309@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox