Date: Sat, 14 Aug 2004 23:21:12 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-current@freebsd.org Subject: Re: MySQL on -current (possible gcc issue?) Message-ID: <20040814232007.R6429@carver.gumbysoft.com> In-Reply-To: <20040814004938.GA26808@parodius.com> References: <20040814004938.GA26808@parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 13 Aug 2004, Jeremy Chadwick wrote: > The issue is that MySQL (4.0.x, 4.1.x, and 5.x) all sig11 on machines > which lack a defined CPUTYPE in make.conf (which translates over to a > missing -march flag to gcc during compile-time). I've confirmed this > on two -current machines, and one 5.2.1-RELEASE machine, all with > different hardware and different configurations. The 5.2.1-RELEASE > test I did solely to see if it was due to the latest gcc -- doesn't seem > to be. Also, WITH_PROC_SCOPE_PTH makes no difference either. I believe there was a fix committed to the MySQL main tree and a snapshot generated that fixed this bug, and another involving libpthread. I don't recall what the problem is, but I suspect some code that made assumptions about optimization that didn't hold when compiled more generically. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040814232007.R6429>