From owner-freebsd-current@FreeBSD.ORG Sun Aug 15 06:21:12 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 6C22C16A4CE for ; Sun, 15 Aug 2004 06:21:12 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 612AD43D31 for ; Sun, 15 Aug 2004 06:21:12 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 557CC72DD4; Sat, 14 Aug 2004 23:21:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 52F7B72DCB; Sat, 14 Aug 2004 23:21:12 -0700 (PDT) Date: Sat, 14 Aug 2004 23:21:12 -0700 (PDT) From: Doug White To: Jeremy Chadwick In-Reply-To: <20040814004938.GA26808@parodius.com> Message-ID: <20040814232007.R6429@carver.gumbysoft.com> References: <20040814004938.GA26808@parodius.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: MySQL on -current (possible gcc issue?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Aug 2004 06:21:12 -0000 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