Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Chris Faylor Date: Mon, 18 Sep 2000 11:43:17 -0400 To: "'cygwin@sources.redhat.com'" Subject: Re: linking against shared libraries Message-ID: <20000918114317.A3239@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: "'cygwin@sources.redhat.com'" References: <779F20BCCE5AD31186A50008C75D99791717A2@silldn_mail1.sanwaint.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <779F20BCCE5AD31186A50008C75D99791717A2@silldn_mail1.sanwaint.com>; from EFifer@sanwaint.com on Mon, Sep 18, 2000 at 11:11:21AM +0100 On Mon, Sep 18, 2000 at 11:11:21AM +0100, Fifer, Eric wrote: > >Chris Faylor wrote: >>I hope that we can resolve whatever issues there are in dl* for cygwin. > >Just as a testimonial, Perl uses the dl* routines successfully. > >Also, if you bypass dlopen() and go straight to LoadLibrary(), >fork() will not work correctly. Right. Unless I wanted to provide a wrapper for LoadLibrary (which I don't) this will always be the case. The problem is that, for some reason, Windows loads DLLs in different spots in the "parent" and "child" when you do a "fork". It has every right to do this, of course, but it screws up fork. I went to considerable effort to work around this last year by instituting an ugly hack in the fork code which worked around this. My main motivation for getting this working was perl since I am a very long time perl user. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com