From owner-freebsd-current@FreeBSD.ORG Sun Sep 5 13:16:08 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 AFE2016A4CF for ; Sun, 5 Sep 2004 13:16:08 +0000 (GMT) Received: from mail.parodius.com (mail.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CC7F43D41 for ; Sun, 5 Sep 2004 13:16:08 +0000 (GMT) (envelope-from jdc@pentarou.parodius.com) Received: from pentarou.parodius.com (jdc@localhost [127.0.0.1]) by mail.parodius.com (8.12.11/8.12.11) with ESMTP id i85DG8tN093996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 5 Sep 2004 06:16:08 -0700 (PDT) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.12.11/8.12.11/Submit) id i85DG8Qq093995 for current@freebsd.org; Sun, 5 Sep 2004 06:16:08 -0700 (PDT) (envelope-from jdc) Date: Sun, 5 Sep 2004 06:16:08 -0700 From: Jeremy Chadwick To: current@freebsd.org Message-ID: <20040905131608.GA93905@parodius.com> Mail-Followup-To: current@freebsd.org References: <20040903013424.GA57576@e-Gitt.NET> <20040903014625.GB57576@e-Gitt.NET> <20040903023846.GA95115@parodius.com> <20040905125944.GD38513@e-Gitt.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040905125944.GD38513@e-Gitt.NET> User-Agent: Mutt/1.5.6i Subject: Re: mysql on recent RELENG_5 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, 05 Sep 2004 13:16:08 -0000 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. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. | On Sun, Sep 05, 2004 at 02:59:44PM +0200, Oliver Brandmueller wrote: > Hi. > > On Thu, Sep 02, 2004 at 07:38:46PM -0700, Jeremy Chadwick wrote: > > What's yet to be discussed by anyone is _why_ -march is required for > > this to work. Is this a gcc-related problem? It's incredibly easy to > > reproduce. > > I agree with you. With 5.3-RELEASE people will expect MySQL to work out > of the box (read: from the package or from ports without tweaking > make.conf) on FreeBSD. > > There's an open bug report ports/70889 on this topic, though it's not > very general, but I think it won't help opening a second one. > > - Oliver > > -- > | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | > | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | > | Ich bin das Internet. Sowahr ich Gott helfe. | > | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! |