From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko Schocher Date: Mon, 04 Oct 2010 10:06:15 +0200 Subject: [U-Boot] denx/master is not building for OMAP3 platforms except Beagle In-Reply-To: <4CA976E4.4020104@dawes.za.net> References: <19F8576C6E063C45BE387C64729E739404AA21C49A@dbde02.ent.ti.com> <4CA96D82.9080000@denx.de> <4CA976E4.4020104@dawes.za.net> Message-ID: <4CA98AF7.9080309@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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