[coreboot] SimNOW V2 LAB problem

[Marc Karasek]

All,

With a little input from Ward,  I think I have found out why I am seeing 
the .ram/.rom can't allocated linking problems. 

It has to do with binutils.  I made a cross-compile setup for i686 with 
gcc 4.1 and binutils 2.16.  This compiles the image properly with no 
errors.

M suggestion would be to setup a cross-compile toolchain for x86 and 
then setup buildrom to use this chain.  I used crosstools to build the 
toolchain.  I have used it in the past and it is a good tool.

If we use this setup, no matter what distro someone is using we can 
always be assured what gcc/binutils/glibc version they are compiling 
coreboot with. 

If you want I can help with a wiki on how to setup a cross-compile 
enviroment using the crosstools scripts.

Marc

*********************
Marc Karasek
MTS
Sun Microsystems
mailto:marc.karasek at sun.com
ph:770.360.6415
*********************



Marc Karasek wrote:
> Ward, et all,
>
> I have completed the test builds on my 32 bit machine.   Tried Filo, 
> tint, coreinfo and LAB.  All were built with the latest coreinfo 
> code.  The version (3092) assoc with the SimNOW platform build does 
> not have the lxbios in the tree and fails the checkout during the build.
>
> What I have seen is that coreboot fails on final link with either
> .ram can't be allocated in segment 0
> or
> .rom can't be allocated in segment 0
>
> The only diff is the Config.lb file I used for coreboot.
>
> I have attached both files.
>
> One I had modified and the other is the original off a fresh 
> checkout.  (The only change was payload.elf -> payload.elf.lzma)
>
> Maybe I am doing something wrong  in configuring coreboot..
>
> Tinit & Coreinfo  both crashed on linking.  Both errors were the same:
> ld terminated with signal 11 [Segmentaion Fault]
>
> Marc
>
> *********************
> Marc Karasek
> MTS
> Sun Microsystems
> mailto:marc.karasek at sun.com
> ph:770.360.6415
> *********************
>
>
>
> Ward Vandewege wrote:
>> On Tue, May 13, 2008 at 04:27:40PM -0400, Marc Karasek wrote:
>>  
>>> What version of binutils? The problem I am seeing on the 32 bit 
>>> system seems to be a linker problem. My gcc is 4.1.2, I am leaning 
>>> towards binutils,  I have 2.17.50.0.18-1 20070731.
>>>     
>>
>> Aha.
>>
>> $ dpkg -l |grep binutils
>> ii  binutils                          2.16.1cvs20060117-1ubuntu2.1
>> The GNU assembler, linker and binary utiliti
>>
>> That's (a lot) older.
>>
>> Thanks,
>> Ward.
>>
>>