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: Mon, 21 Oct 2002 10:33:39 -0400
From: Jason Tishler <jason AT tishler DOT net>
Subject: Re: latest cvs fork problems
In-reply-to: <3.0.5.32.20021019091806.0081b960@mail.attbi.com>
To: cygwin AT cygwin DOT com
Mail-followup-to: cygwin AT cygwin DOT com
Message-id: <20021021143339.GB1456@tishler.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.4i
References: <3 DOT 0 DOT 5 DOT 32 DOT 20021019091806 DOT 0081b960 AT mail DOT attbi DOT com>

Pierre,

The following is moot and mainly for the achives...

On Sat, Oct 19, 2002 at 09:18:06AM -0400, Pierre A. Humblet wrote:
> Jason Tishler wrote
> $ ps -ef
>     exim     648    1096   ?  16:18:22 /usr/local/bin/exim-4.10-1
> 
> That's probably a privately compiled exim. 

Yes, I'm still using a private exim build.  Sorry, but I haven't
switched the official one yet -- changing MTAs is a little disruptive.

> Does it use special libraries/dll (perl, ...)?

I just built a stock exim 4.10 using the normal exim build procedure.
Nevertheless, my build is dependent on (a static) bind and has the
following Cygwin DLL dependencies:

    $ cygcheck exim-4.10-1.exe | fgrep -i cygwin
    Found: C:\cygwin\usr\local\bin\exim-4.10-1.exe
      C:\cygwin\bin\cygwin1.dll
      C:\cygwin\bin\cyggdbm.dll
      C:\cygwin\bin\libperl5_6_1.dll

Jason

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/