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: <007a01c2d6e8$9f090380$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: <Pine DOT GSO DOT 4 DOT 44 DOT 0302171935300 DOT 7773-100000 AT slinky DOT cs DOT nyu DOT edu>
Subject: Re: Obtaining a pervious version
Date: Tue, 18 Feb 2003 00:56:50 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Igor Pechtchanski wrote:
> John,
>
> FYI, if you simply copy the DLL, the programs will try to load it
> twice (once for each name).  As I see it, you have the following
> choices:
>
> 1) Check out from CVS with the "cygwin-1-3-13-1" or "cygwin-1-3-13-2"
>    tag (depending on the version they used) and compile a xygwin1.dll
>    with a different shared memory region name.

Um?

First, the cygwin CVS tags are for cgf's private use, and are not guaranteed
to correspond exactly to releases. Also, they don't reach the sources
outside of winsup.

Second, if he were to get the Cygwin sources, he would be compiling
*c*ygwin1.dll.

Actually, building a replacement *x*ygwin1.dll (with different shared memory
ID) from the *x*ygwin source tarball might be the easiest option.

> 2) Compile your own cygwin1.dll from CVS or sources (search the list
>    for instructions) with a different shared memory region name.

> 3) Recompile your toolset (as Max recommended).
>
> If I were you, I'd go with choice #1, as it'll be easier to update
> cygwin1.dll after that, and it doesn't involve the effort of
> recompiling the whole toolset.  Choice #3 is probably the most
> prudent in the long run, though.

#3 is certainly the conventional way to do it. But maybe, if you made an
alternate xygwin1.dll with different shared memory id, you could submit the
patch to xilinx, and then once they re-released, you wouldn't have the
problem any more?

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/