Re: [LinuxBIOS] r3021 build service

[Myles Watson]

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

On Dec 20, 2007 12:19 PM, Marc Jones  wrote:
> Corey Osgood wrote:
> > Corey Osgood wrote:
> > > On Dec 19, 2007 4:26 PM, LinuxBIOS information <[e-mail]
> > > > 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 < [e-mail]
> > > <mailto:[e-mail]>>
> > > Acked-by: Corey Osgood <[e-mail]
> > > <mailto:[e-mail]>>
> > >
> > >
> > >
> > > 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