Here's my attempt at fixing abuild for serengeti_cheetah_fam10. It's pretty trivial, since I'm just using the ROM_IMAGE_SIZE in Config.lb and putting it in Config-abuild.lb. When I reduce this size (past what it is in Config-abuild.lb), it gives me the same overlap error in my system that abuild is seeing.
I also added XIP_ROM_SIZE, although I admit freely that I don't know anything about this variable. I just wanted to make it match Marc's Config.lb. Maybe the right thing to do would be to remove both XIP_ROM_SIZE references in Config-abuild.lb Either way, I think the ROM_IMAGE_SIZE change will help. Myles Signed-off-by: Myles Watson <[EMAIL PROTECTED]> On Dec 20, 2007 12:19 PM, Marc Jones <[EMAIL PROTECTED]> wrote: > > Corey Osgood wrote: > > Corey Osgood wrote: > > > >> On Dec 19, 2007 4:26 PM, LinuxBIOS information <[EMAIL PROTECTED] > >> <mailto:[EMAIL PROTECTED]>> wrote: > >> > >> Dear LinuxBIOS readers! > >> > >> This is the automated build check service of LinuxBIOS. > >> > >> The developer "cozzie" checked in revision 3021 to > >> the LinuxBIOS source repository and caused the following > >> changes: > >> > >> Change Log: > >> More abuild fixes, this should be the last (trivial) > >> > >> Signed-off-by: Corey Osgood < [EMAIL PROTECTED] > >> <mailto:[EMAIL PROTECTED]>> > >> Acked-by: Corey Osgood <[EMAIL PROTECTED] > >> <mailto:[EMAIL PROTECTED]>> > >> > >> > >> > >> Build Log: > >> Compilation of amd:serengeti_cheetah_fam10 is still broken > >> See the error log at > >> > >> http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_cheetah_fam10&vendor=amd > >> > >> <http://qa.linuxbios.org/log_buildbrd.php?revision=3021&device=serengeti_cheetah_fam10&vendor=amd> > >> > >> > >> Oh for cripe's sake, ld now? Will fix when I make it home tonight. > >> > >> -Corey > >> > > > > Scratch that, someone else can wrap it up. I don't know if it just needs > > a ROM_SIZE increase or something deeper is wrong, I've been completely > > unable to reproduce the error. Someone with access to the build server > > or a similar setup is probably the best candidate to fix this (I've done > > my share ;-) ) > > > > -Corey > > > > > > Corey, > > I looked at the output and I don't see anything obvious. It doesn't fail > for me either. I'll work with Stefan when he is able to look at it. > > Marc > > -- > Marc Jones > Senior Firmware Engineer > (970) 226-9684 Office > mailto:[EMAIL PROTECTED] > http://www.amd.com/embeddedprocessors > > > > > > -- > linuxbios mailing list > linuxbios@linuxbios.org > http://www.linuxbios.org/mailman/listinfo/linuxbios >
Index: targets/amd/serengeti_cheetah_fam10/Config-abuild.lb =================================================================== --- targets/amd/serengeti_cheetah_fam10/Config-abuild.lb (revision 3046) +++ targets/amd/serengeti_cheetah_fam10/Config-abuild.lb (working copy) @@ -13,7 +13,8 @@ romimage "fallback" option USE_FALLBACK_IMAGE=1 - option ROM_IMAGE_SIZE=0x20000 + option ROM_IMAGE_SIZE=0x3f000 + option XIP_ROM_SIZE=0x40000 option LINUXBIOS_EXTRA_VERSION=".0-fallback" payload __PAYLOAD__ end @@ -26,4 +27,4 @@ option LINUXBIOS_EXTRA_VERSION=".0-failover" end -buildrom ./linuxbios.rom ROM_SIZE "fallback" "failover" \ No newline at end of file +buildrom ./linuxbios.rom ROM_SIZE "fallback" "failover"
-- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
