Re: GCC 4.5 testing -- your help wanted

[Frank Kardel <Frank.Kardel%kardel.name@localhost>]

Great !

I did a quick build release on amd64-current for -current.

Two issues where seen:
        1) build with USE_SSP=yes fails (cannot protect variable sized array)
        2) build with MKDTRACE=yes uncovers two files in solris/dtrace code
           where gcc45 suspects use of possibly uninitialized variables

Without USE_SSP=yes and fixes for the possibly uninititialized warning build
is fine.

Frank

On Sun, Jul 17, 2011 at 09:42:03PM +1000, matthew green wrote:
> 
>  ...
> it's pretty simple.  all you have to do is set HAVE_GCC=45 when building
> the system. (eg, ./build.sh -V HAVE_GCC=45).  it's best to ensure a
> cleandir before making this switch but it seems that technically only
> src/tools/gcc and the destdir need to be cleaned for a build to succeed
> (but this will not result in everything being rebuilt with the new
> compiler.)
> 
> please let this list know about any success or failure you may have,
> including what platform/task/etc you're trying.
> 
> thanks!
> 
> 
> .mrg.