From owner-freebsd-current@FreeBSD.ORG  Tue Mar 23 20:23:52 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 36E6216A4CE; Tue, 23 Mar 2004 20:23:52 -0800 (PST)
Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5A54C43D2D; Tue, 23 Mar 2004 20:23:51 -0800 (PST)
	(envelope-from ganbold@micom.mng.net)
Received: from [202.179.0.164] (helo=ganbold.micom.mng.net)
	by publicd.ub.mng.net with asmtp (Exim 4.30; FreeBSD)
	id 1B5zqj-000Mg3-Gh; Wed, 24 Mar 2004 12:18:41 +0800
Message-Id: <6.0.3.0.2.20040324122232.02a419b0@202.179.0.80>
X-Sender: ganbold@micom.mng.net@202.179.0.80
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Wed, 24 Mar 2004 12:28:40 +0800
To: Alex Dupre <ale@FreeBSD.org>
From: Ganbold <ganbold@micom.mng.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
cc: freebsd-current@freebsd.org
cc: freebsd-ports@freebsd.org
cc: freebsd-threads@freebsd.org
Subject: Re: MySQL 4.0.18 server problem on FreeBSD 5.2-Current
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2004 04:23:52 -0000

Hi Alex,

I tested mysql-4.0.18 server from ports with CPUTYPE=p4 options in 
/etc/make.conf.
I works fine, even tcp connections work fine.
I will wait when comes out mysql-4.0.19 and leave another server with 
latest snapshot of mysql.
Thank you for your great help.

regards,

Ganbold


At 09:41 PM 23.03.2004, you wrote:
>Ganbold wrote:
>
>>Before mysql update was really easy, but now I have big problem.
>>What should do in this case? Is there anybody solved this problem before?
>
>You should read the mailing lists before posting on them...btw, it seems 
>to be a problem with CPUTYPE not set in /etc/make.conf.....currently it is 
>known to work with CPUTYPE=p3 and to not work without CPUTYPE....otherwise 
>you can remove --with-libwrap from your Makefile and loose the tcpwrapper 
>support.
>
>--
>Alex Dupre