[uClibc] Re: Linux2.4.22 for armb with GCC3.4.1 - cores

[Peter S. Mazinger]

> From: "Doug Oucharek" <dougs at broadcom.com>
> Subject: [uClibc] Linux2.4.22 for armb with GCC3.4.1 - cores
> To: uclibc at uclibc.org
> Message-ID:
> 	<24CDBA67F085904999751B3C4F9E8C0B01C4CF19 at NT-RMNA-0740.brcm.ad.broadcom.com>
> 	
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi all,
>  
> I've been working with a toolchain built with gcc3.3.2 and uclibc 0.9.26
> for big endian ARM.  With this toolchain, I've been able to compile and
> run a Linux2.4.22 kernel, drivers, and user space apps.  So far, no
> problems.  
>  
> Recently, however, I've run into the GCC STL issue discussed here:
>  
> http://www.uclibc.org/lists/uclibc/2004-October/010073.html
> http://www.uclibc.org/lists/uclibc/2004-October/010074.html
> http://www.uclibc.org/lists/uclibc/2003-October/007169.html
> http://www.uclibc.org/lists/uclibc/2003-October/007169.html
>  
> In hopes of resolving this, I was told by a co-worker to upgrade the
> toolchain to gcc3.4.1 (is this really necessary?).  I did so, but have
> found that the resulting Linux2.4.22 kernel freezes on startup.  In
> fact, the gunzip process to unload the compressed kernel isn't even
> working properly (crc does not check match).  I recompiled just that
> part with gcc3.3.2 and now the kernel unloads but then freezes when it
> starts.
>  
> I ran readelf -a on vmlinux compiled with gcc3.3.2 and with gcc3.4.1 and
> the header information matches so I feel the endianess is correct.  
>  
> Just for fun, I compiled the kernel with gcc3.3.2 and the user space
> apps with gcc3.4.1.  Everything ran fine so the compiler is creating
> code which works on my ARM platform.

that should be fine, to have a kernel built w/ gcc-3.4, you have to use at 
least 2.4.28-pre2-bk2 or newer (haven't tried that on arm though)

Peter

-- 
Peter S. Mazinger <ps dot m at gmx dot net>           ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08  BB6E C389 975E A5F0 59F2