From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Multiple cygwins/ Distributing cygwin apps
Date: Fri, 07 Nov 2003 16:05:00 -0000 [thread overview]
Message-ID: <20031107160521.GA32632@redhat.com> (raw)
In-Reply-To: <boempl$810$1@sea.gmane.org>
The correct solution for dealing with multiple cygwins on your system
is to remove all of the older DLLs.
If you have a distribution which distributes cygwin and that distribution
screws up an existing cygwin installation, then complain to the people
who provided the distribution. Their installation software is broken.
To repeat: There is no need to keep multiple versions of the cygwin
DLL on your system.
I'm closing this thread now.
On Thu, Nov 06, 2003 at 04:51:16PM -0700, John Moore wrote:
>I now have a procedure that works on my system for allowing more than
>one cygwin to exist on the same Windows instance at the same time (but
>not to execute at the same time).
--
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/
next prev parent reply other threads:[~2003-11-07 16:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 2:20 Multiple Cygwins/ Distributing Cygwin apps John Moore
2003-11-03 2:34 ` Gary R. Van Sickle
2003-11-03 2:51 ` Igor Pechtchanski
2003-11-03 3:12 ` Gary R. Van Sickle
2003-11-03 3:52 ` Brian Dessent
2003-11-03 6:27 ` John Moore
2003-11-03 8:24 ` Brian Dessent
2003-11-03 18:42 ` Multiple cygwins/ Distributing cygwin apps Christopher Faylor
2003-11-03 23:41 ` Igor Pechtchanski
2003-11-03 16:38 ` Christopher Faylor
2003-11-06 23:51 ` Multiple Cygwins/ Distributing Cygwin apps John Moore
2003-11-07 16:05 ` Christopher Faylor [this message]
2003-11-03 10:30 kevin.lawton
2003-11-03 17:46 Multiple cygwins/ Distributing cygwin apps kevin.lawton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031107160521.GA32632@redhat.com \
--to=cgf-no-personal-reply-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).