Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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:	<40C97B01.DB0AF91A@dessent.net>
Date:	Fri, 11 Jun 2004 02:27:29 -0700
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Tivoli
References:	<F0D7281DAB048B438E8F5EC4ECEFBDDC1760B2 AT esmail DOT elsag DOT de>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id i5B9RDfF009426

Jörg Schaible wrote:

> This is not recommended. http://cygwin.com/faq/faq_4.html#SEC51
> 
> The cygwin core uses shared memory and it does not matter if you separate the two dlls with paths or rename on or ... two of these dll's will always influence each other - even if it is the same version. As a rule of dumb: Use always the same dll on one machine.
> 
> The only solution would be to build an own cygwin1.dll that is named differently and uses internally another location of the shared memory.

If it were me I'd delete all of them except for the latest 1.5.10, as
the DLL is theoretically backwards compatible so something compiled
against 1.3.x should work with the current but not vice versa.  Or so I
seem to remember reading.  However since cgf has already voiced his
disapproval of us using this list to give free Tivoli support, I suppose
this is now wandering OT ...

Brian

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