Re: Critical mysql bug = remotely changing from PURE64 to 32-bit debian.. possible?

[Jeremy Gray <Jeremy@jpgsworld.com>]

Frederik Schueler wrote:

> Hello,
>
> is this bug reproducible only if the highly experimental gcc-3.4/gcc-4.0
> branch is used, as stated in the quoted mysql-bts bugs, or does this 
> happen using a standard debian-pure64 (gcc-3.3 based) installation too?
>
> A quote from mysql bug #3483:
>  
>
> > I've tried 4.0.23, 4.1.9, 4.1.10 on two dual opterons with 8 gig ram
> > running Debian 3.1 pure64 gcc3.4. Tried kernels 2.6.11-rc1-mm1 and 
> > 2.6.11-rc2.
> >    
>
> the gcc-3.4 (now gcc-4.0) branch is based on an unreleased, experimental
> compiler version (http://gcc.gnu.org/gcc-4.0/). The code is likely to 
> break and _not intended for production_. 
>
> Again: if you want to run a production system with 64bit userland, pick
> debian-pure64, and not the experimental gcc-3.4/gcc-4.0 based branch.
>
>
> Kind regards
> Frederik Schueler
>
>  

I haven't tried running it yet myself, but I am just on the 
Debian-Pure64 branch.

I did see the notices that gcc-3.4 is experimental.

I first came across the notice of this bug at Joe Stumps page:
http://www.joestump.net/193251484/running-apache-mysql-php-on-debian-amd64.html

Not sure what version he was running, but he put a comment in on the bug 
too.

So it might be fine in Pure64 mode then?

Thanks