Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 28 May 2003 18:48:52 +0200
From: "Gerrit P. Haase" <gerrit AT familiehaase DOT de>
Reply-To: "Gerrit P. Haase" <gerrit AT familiehaase DOT de>
Organization: Esse keine toten Tiere
X-Priority: 3 (Normal)
Message-ID: <47540687307.20030528184852@familiehaase.de>
To: linamat AT moldtelecom DOT md
CC: cygwin AT cygwin DOT com
Subject: Re: qmail cygwin port successfull
In-Reply-To: <1346.212.0.200.22.1054133128.mtc@mail.moldtelecom.md>
References: 
 <1214 DOT 212 DOT 0 DOT 200 DOT 22 DOT 1054121128 DOT mtc AT mail DOT moldtelecom DOT md><35526029740.200
 30528144435 AT familiehaase DOT de><1247 DOT 212 DOT 0 DOT 200 DOT 22 DOT 1054126724 DOT mtc AT mail DOT mol
 dtelecom.md> <55531327899 DOT 20030528161253 AT familiehaase DOT de>
 <1346 DOT 212 DOT 0 DOT 200 DOT 22 DOT 1054133128 DOT mtc AT mail DOT moldtelecom DOT md>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit

Hello,

I wrote:
>> The client is not the problem, I have compiled my own version of MySQL,

You wrote:
> Anyhow what mysql you want to use, libmysqlclient.dll from mysql sources
> is recommended (not from mysql-xxxx-win32.src). For vpopmail/vmailmgr, I
> mean.

I have compiled mysql-4.1.0-alpha with dynamic clientlibs and with the
server as static binary, all 'pure' Cygwin versions, but the server
crashes with the latest Cygwin version.


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/