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
Message-ID:	<006c01c2d6e5$716b0890$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	<cygwin AT cygwin DOT com>, "John Williams" <jwilliams AT itee DOT uq DOT edu DOT au>
References:	<3E5024EE DOT 400 AT itee DOT uq DOT edu DOT au> <20030217145707 DOT GA3647 AT redhat DOT com> <3E51599B DOT 5090301 AT itee DOT uq DOT edu DOT au> <001401c2d6d0$6102a4a0$78d96f83 AT pomello> <3E5163E3 DOT 7000605 AT itee DOT uq DOT edu DOT au> <001701c2d6d6$403696e0$78d96f83 AT pomello> <20030217224649 DOT GA18908 AT redhat DOT com> <3E516C10 DOT 8050309 AT itee DOT uq DOT edu DOT au> <003101c2d6da$adc26cd0$78d96f83 AT pomello> <20030217233207 DOT GA18885 AT redhat DOT com> <20030217233946 DOT GB18885 AT redhat DOT com> <3E517569 DOT 1060800 AT itee DOT uq DOT edu DOT au> <3E517A16 DOT 9050500 AT rfk DOT com> <3E517E2F DOT 6020705 AT itee DOT uq DOT edu DOT au>
Subject:	Re: Obtaining a pervious version
Date:	Tue, 18 Feb 2003 00:34:04 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

John Williams wrote:
> Larry Hall (RFK Partners, Inc.) wrote:
>>
>> What doesn't work?  The Cygwin provided utilities or the Xygwin1
>> versions?
>
> Neither.  I can't run either Cygwin utilities under Xygwin, nor the
> Xygwin utilities under Cygwin.  Full error messages were posted
> earlier in the thread.

And Chris Faylor explained them. The Xygwin people didn't bother to change
the shared memory ID, so, in fact changing the DLL name was pointless. All
the usual issues (i.e. it is impossible) involved with multiple versions of
cygwin1.dll still apply in this case.

>> I wouldn't necessarily expect the Cygwin utilities to work in this
>> situation, since they may be using something in the newer
>> cygwin1.dll.
>
> Hence my original question about winding back the clock.

Won't help, for reason above.

>> I suppose you could always use  strace if this doesn't answer the
>> "it doesn't work" question.
>
> Good tip. Thanks, I'll give it a try.

Won't help - we know the problem already - as above - multiple DLL versions
trying to use the same shared resources.

Max.


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

- Raw text -