From owner-freebsd-current@FreeBSD.ORG Sun Sep 5 14:03:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B35E116A4CE for ; Sun, 5 Sep 2004 14:03:47 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6636643D3F for ; Sun, 5 Sep 2004 14:03:47 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) i85E3kjf000727; Sun, 5 Sep 2004 10:03:46 -0400 (EDT) Date: Sun, 5 Sep 2004 10:03:46 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Jeremy Chadwick In-Reply-To: <20040905131608.GA93905@parodius.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) cc: current@freebsd.org Subject: Re: mysql on recent RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2004 14:03:47 -0000 On Sun, 5 Sep 2004, Jeremy Chadwick wrote: > I agree, opening another bug report on this probably wouldn't do much. > However, the only places I've seen it mentioned are here on -current. > > ports/70889 is also for the alpha architecture, which may (possibly?) be > seeing a different error message depending upon what sort-of code is > being generated. > > I don't "mind" having to use CPUTYPE as a workaround (I'm glad there's > one at all!); I'm mainly worried that the MySQL folks will begin claiming > that "FreeBSD isn't suited for MySQL" because of this problem, or > something along those lines. There's enough public misnomers as-is > about MySQL on FreeBSD (even a few on the official MySQL site). > > I'm more than happy to test patches or give someone access to our 5.x > SQL box if they want to try and track this down. I seem to recall someone mentioning that this was a compiler bug that was fixed (worked around) in mysql (CVS?) sources. It might have been posted over on threads@, but I can't recall. -- Dan