[coreboot] SimNOW V2 LAB problem
jordan.crouse at amd.com
Fri May 9 18:01:32 CEST 2008
On 09/05/08 11:41 -0400, Marc Karasek wrote:
> I d/l buildrom to my notebook to build a 32bit version to try it with
> SimNOW. It compiles but gets a linker error :
> <coreboot: section `.ram' can't be allocated in segment 0>
> Any thoughts on what could be causing this???
This is from coreboot itself? That sounds really evil.
We clearly have some major toolchain churn here.
> Marc Karasek
> Sun Microsystems
> mailto:marc.karasek at sun.com
> Jordan Crouse wrote:
>> On 08/05/08 20:32 -0400, Ward Vandewege wrote:
>>> On Thu, May 08, 2008 at 03:52:21PM -0600, Myles Watson wrote:
>>>>> Disregard my feeble wanderings.. I was thinking about my attempt to
>>>>> move busybox to 1.10.1 and the problems I was seeing there.
>>>>> I think though the two are related. Seems that uClibc 0.9.29 no longer
>>>>> supports the toolchain wrappers for -nostdlib and forcing a linking
>>>>> native tools (gcc/binutils) and a compiled uClibc library. This was
>>>>> pulled in 0.9.22 according to the uclibc FAQ. Maybe it was just a one
>>>>> off that FC5 still worked.
>>>> Strange. It worked for 0.9.28 as well. Those are the two versions I've
>>>> used in buildrom.
>>>> Ward: You've used lab haven't you? What toolchain do you use?
>>> Yep, I've got LAB systems running. I build on gNewsense deltad typically,
>>> which is basically Ubuntu Dapper, 32 bit.
>> It might be time for us to ping the uClibc / busybox teams for some
Systems Software Development Engineer
Advanced Micro Devices, Inc.
More information about the coreboot