[Trac #120] buildrom fails on fc5

[Zarro Boogs per Child]

#120: buildrom fails on fc5
-----------------------+----------------------------------------------------
 Reporter:  dilinger   |        Owner:  rminnich
     Type:  defect     |       Status:  new     
 Priority:  normal     |    Milestone:          
Component:  linuxbios  |   Resolution:          
 Keywords:             |  
-----------------------+----------------------------------------------------
Comment (by rsmith):

 Replying to [comment:4 rminnich]:
 > It's not really lzma that is the issue, this is still some kind of weird
 toolchain issue. I can build on fc5 just fine with lzma.
 > I need a login on a failing machine.

 Ron is correct.  I spend a lot of time looking at this tonight.  Lzma is
 just the straw that broke the camels back.

 The linuxbios size rom size is set in the config file at 32k.  A lzma
 build on my Debian Testing machine ends up with about 0x99 bytes free in
 that area.

 When you build with the FC5 toolchain the resulting image is just a wee
 bit larger this extra size causes a section overlap and breaks the build.

 When I increase the linuxbios rom image size from 32k to 33k things build
 fine for my on learn.laptop.org where previously they would break.

 Heres and objdump between the stock build on my Debian Testing machine and
 sucessful build on learn.

 Richard's Debian box:

 {{{
 ./fallback/linuxbios:     file format elf32-i386

 Sections:
 Idx Name          Size      VMA       LMA       File off  Algn
   0 .ram          00007106  ffff8000  ffff8000  00001000  2**0
                   CONTENTS, ALLOC, LOAD, DATA
   1 .rom          00000e3a  fffff106  fffff106  00008106  2**4
                   CONTENTS, ALLOC, LOAD, READONLY, CODE
   2 .reset        00000010  fffffff0  fffffff0  00008ff0  2**0
                   CONTENTS, ALLOC, LOAD, READONLY, DATA
   3 .id           00000017  ffffffd9  ffffffd9  00008fd9  2**0
                   CONTENTS, ALLOC, LOAD, READONLY, DATA
 }}}

 Learn.laptop.org with a 33k linuxbios size.

 {{{
 ./fallback/linuxbios:     file format elf32-i386

 Sections:
 Idx Name          Size      VMA       LMA       File off  Algn
   0 .ram          0000719f  ffff7c00  ffff7c00  00000c00  2**0
                   CONTENTS, ALLOC, LOAD, DATA
   1 .rom          00000e41  ffffed9f  ffffed9f  00007d9f  2**4
                   CONTENTS, ALLOC, LOAD, READONLY, CODE
   2 .reset        00000010  fffffff0  fffffff0  00008ff0  2**0
                   CONTENTS, ALLOC, LOAD, READONLY, DATA
   3 .id           00000017  ffffffd9  ffffffd9  00008fd9  2**0
                   CONTENTS, ALLOC, LOAD, READONLY, DATA
 }}}

 So you can see that the .ram and .rom size on learn is 0xa0 bytes bigger
 than my Debian image.  This was blowing the 0x99 free bytes and
 overlapping segments.

 With the 33k linuxbios size I did not receive any of the wierd objcopy
 problems.

-- 
Ticket URL: <http://dev.laptop.org/ticket/120#comment:5>
One Laptop Per Child <http://laptop.org/>