Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 22 Apr 2004 15:29:00 -0400
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: recompiling cygwin dll problems
Message-ID: <20040422192900.GA4119@coe.bosbc.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20040421222902.GA20113@mdssdev05.comp.pge.com> <6.1.0.6.0.20040421221948.028c5440@127.0.0.1> <20040422182421.GA22635@mdssdev05.comp.pge.com> <6.1.0.6.0.20040422143806.038cf008@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.1.0.6.0.20040422143806.038cf008@127.0.0.1>
User-Agent: Mutt/1.4.1i

On Thu, Apr 22, 2004 at 02:44:47PM -0400, Larry Hall wrote:
>>Or maybe its neither a nor b.. perhaps there's a runtime component? Perhaps you 
>>can't run two versions of the cygwin dll at one time in separate locations?
>
>Bingo!  I guess I should have put an "and" in my first two statements.
>You can only have *1* DLL built from the Cygwin source resident and 
>running at any one time.  It wasn't clear to me that this is what you 
>were doing, otherwise I would have told you that this is a no-no to 
>start with.

Actually, that isn't entirely true or you wouldn't be able to run the
test suite.  Looking at the test suite scripts might be instructive.

cgf
(Who knows he'll regret even mentioning this)

--
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/