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
Reply-To:	Cygwin List <cygwin AT cygwin DOT com>
Message-Id:	<6.1.0.6.0.20040422143806.038cf008@127.0.0.1>
X-Sender:
Date:	Thu, 22 Apr 2004 14:44:47 -0400
To:	"Edward S. Peschko" <esp5 AT pge DOT com>, Cygwin List <cygwin AT cygwin DOT com>
From:	Larry Hall <cygwin-lh AT cygwin DOT com>
Subject:	Re: recompiling cygwin dll problems
In-Reply-To:	<20040422182421.GA22635@mdssdev05.comp.pge.com>
References:	<20040421222902 DOT GA20113 AT mdssdev05 DOT comp DOT pge DOT com> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040421221948 DOT 028c5440 AT 127 DOT 0 DOT 0 DOT 1> <20040422182421 DOT GA22635 AT mdssdev05 DOT comp DOT pge DOT com>
Mime-Version:	1.0

At 02:24 PM 4/22/2004, you wrote:
>On Wed, Apr 21, 2004 at 10:21:58PM -0400, Larry Hall wrote:
>> At 06:29 PM 4/21/2004, you wrote:
>> >all,
>> >
>> >Is there any reason why a recompiled version of cygwin.dll in a non-standard location
>> >would cause tools that depend on it to fail? I compiled with a standard:
>> >
>> >configure --prefix=<my_prefix>
>> >make
>> >make install
>> >
>> >I need to remove the compiled dll in order to get anything working again...
>> >
>> >Also, any debugging tips on tracking this down? If its there, none of the tools
>> >work (gdb included), if its not, they don't..
>> >
>> 
>> 
>> Make sure the tools can see the DLL.  Make sure the old DLL is not 
>> accessible by *any* of the tools.  Make sure the new DLL is valid. ;-)
>
>Well:
>
>:) they can see the dll, since when I create the dll, everything stops working.
>
>2) I'm pretty sure its not the old dll, since when I rename the old dll, everything 
>still stops working.
>
>3) hence I'm assuming #3 - the new DLL isn't valid.
>
>I know I'm being vague, but it would be a lot easier for me to issue a bug report/fix
>if I had a good way of debugging the cygwin dll. The person who would have an answer
>to that question is the writer/maintainer of the cygwin dll who hopefully 
>chime in at some point as to:
>
>    a) some debugging tips on how to track down cygwin related problems.
>
>    b) whether or not there are some hard-coded values in the cygwin code that 
>       need to be changed to make them portable to different directories.
>
>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.


> 
>Just guessing here, but enquiring minds want to know...


Good guess. ;-)



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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

- Raw text -