Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Mime-Version: 1.0 (Apple Message framework v618) In-Reply-To: <20040528171500.GC26698@coe.bosbc.com> References: <20040527212657.GC2617@ata.cs.hun.edu.tr> <7F99F48A-B0C5-11D8-BB92-000A95C4BF56@cipheroptics.com> <20040528171500.GC26698@coe.bosbc.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Michael Hale Subject: Re: dll version collision Date: Fri, 28 May 2004 13:31:34 -0400 To: cygwin@cygwin.com X-OriginalArrivalTime: 28 May 2004 17:31:57.0798 (UTC) FILETIME=[AD38A860:01C444D9] X-IsSubscribed: yes On May 28, 2004, at 1:15 PM, Christopher Faylor wrote: > On Fri, May 28, 2004 at 12:38:50PM -0400, Michael Hale wrote: >> The ideas suggested here are definitely beyond my current ability. I >> hope someone else who would like this done, and has the skill will >> take >> it up. > > If it is beyond your abilities then you shouldn't be considering this > option. This is likely never to be an accepted way of using the cygwin > DLL. What is the correct way for someone to run multiple versions of cygwin on their machine then? This seems like a very useful feature to me, since among other uses it would allow a new version to be tested along side an older but known version of cygwin. > -- > Christopher Faylor spammer? -> aaaspam@sourceware.org > Cygwin Co-Project Leader aaaspam@duffek.com > TimeSys, Inc. > > -- > 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/ > > "OS X: because it was easier to make UNIX user-friendly than to fix Windows" -- 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/