On 20.01.2008 02:11, coreboot information wrote:
Change Log: give it 2k more space for abuild. let's look into this anyways, but get rid of the impression that the cheetah on fam10 is broken just because we're using a too new compiler for abuild. (trivial)
Signed-off-by: Stefan Reinauer stepan@coresystems.de Acked-by: Stefan Reinauer stepan@coresystems.de
Build Log: Compilation of amd:serengeti_cheetah_fam10 is still broken See the error log at http://qa.linuxbios.org/log_buildbrd.php?revision=3065&device=serengeti_...
Last part of the diff between the r3064 log and the r3065 log follows:
gcc -m32 -nostdlib -nostartfiles -static -o coreboot -T ldscript.ld crt0.o -/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: section .id [00000000ffffefd2 -> 00000000ffffefef] overlaps section .rom [00000000fffeed6d -> 00000000ffffff4f] +/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: section .id [00000000ffffefd2 -> 00000000ffffefef] overlaps section .rom [00000000fffee571 -> 00000000fffff74f] /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: coreboot: section .id lma 0xffffefd2 overlaps previous sections /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: coreboot: section .reset lma 0xffffeff0 overlaps previous sections
You have to move section .rom another 2k down (2k more space) to get it to build. New value that should work: ROM_IMAGE_SIZE='0x21000'
Regards, Carl-Daniel