misc/63213: MySQL 4 crashes on CURRENT since 20040221

[Erik Greenwald]

On Tue, Feb 24, 2004 at 07:15:45PM -0800, Kris Kennaway wrote:
> On Tue, Feb 24, 2004 at 07:31:34PM +0100, Gabriel Ambuehl wrote:
> > Hello Erik,
> > 
> > Sunday, February 22, 2004, 4:15:53 PM, you wrote:
> > 
> > > The only thing I did between going from perfectly happy rdbms on
> > > -current 20040207 and sig11 spew in an err file was a portupgrade. I
> > > tried purging and rebuilding the port a couple times to see if there was
> > > build issue, then upgraded world to see if that was the cause... :/
> > > Maybe after I'm done moving and have some time, I'll try to downgrade
> > > world to a pre-kse kernel. 
> > 
> > MySQL 4.0.18 works perfectly on 5.2.1RC2. I'm now updating to CURRENT
> > to see what's going on.
> 
> Have you rebuilt all your ports to deal with the libpthread relinking in -CURRENT?
> 
> Kris

yes, after it crashed, I purged and rebuilt all the ports. I'll
try it again when I get some time to see what happens.

I gave it a shot on my (p4) work box, and had no issues with it. When I
get some time, I'll also try backing the cputype/cflags down to
something less assumptive than the current default.

Time, however, is something I'm short on at the moment; busy moving in
to a new house :)

-- 
        -Erik <erik at smluc.org> [http://math.smsu.edu/~erik]

The opinions expressed by me are not necessarily opinions. In all probability,
they are random rambling, and to be ignored. Failure to ignore may result in
severe boredom or confusion. Shake well before opening. Keep Refrigerated.