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: <4.3.1.2.20021224084949.017219b0@pop.rcn.com>
X-Sender: lhall AT pop DOT rcn DOT com
Date: Tue, 24 Dec 2002 09:00:01 -0500
To: "Pharas" <pharas AT centurytel DOT net>, <cygwin AT cygwin DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: RE: Running cygwin built programs in Windows XP
In-Reply-To: <000901c2ab21$53c2c8e0$e9f3fea9@home7wuwb5xa1g>
References: <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20021222213004 DOT 01ef7bc8 AT pop3 DOT cris DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Pharas,

Letting folks know what you did is fine but it's also the responsibility of 
this list to let everyone know which practices are very error-prone and not
supported by this list.  While we would prefer that everyone was aware of 
the best practices for Cygwin installations, we recognize that this isn't 
ever going to be the case.  So certain suggestions, like yours, will occur
even though such changes are very highly discouraged and folks making those
changes won't receive much in the way of real support for any issues they 
may post until the change is reverted.  But I think the point here is simply
that while it's fair for you to make such a suggestion, you should point out
that such a change is not supported by this list.  If you didn't know this 
to be the case, that's OK.  Now you do.  It's our obligation to inform you 
and others of this policy.

To answer your question about the paths and cygwin1.dll, yes, if cygwin1.dll
is in your Windows (system preferably) path, then any Cygwin program anywhere
on your system can be run any time and the DLL will always be found.

Larry


At 02:51 AM 12/24/2002, Pharas wrote:
>Hey I was just letting him know how I did it. Never said it was the correct
>way to do it, because I never knew about the shared memory thing. Ok then I
>have a question, if you can't use -mno-cygwin to compile you just need to
>make sure the path is set correctly and it will work?
>
>-----Original Message-----
>From: Randall R Schulz [mailto:rrschulz AT cris DOT com] 
>Sent: Sunday, December 22, 2002 11:36 PM
>To: cygwin AT cygwin DOT com
>Subject: RE: Running cygwin built programs in Windows XP
>
>Pharas,
>
>Larry is correct. You are not. Problems do occur with multiple copies of 
>Cygwin1.dll on a system. We see it here all the time.
>
>Cygwin relies on a shared memory segment and when there's more than one 
>copy of the DLL on a given system, eventually a second one will get loaded, 
>try to initialize itself and either fail or interfere with the one that's 
>already loaded and initialized.
>
>If you want to do this, it's no skin off our nose, but DON'T recommend that 
>others do so.
>
>Randall Schulz
>
>
>At 20:53 2002-12-22, Pharas wrote:
> >I meant to just copy it not move it outright, as far as unstability I have
> >been using cygwin for quite a long time and have had no probs with this.
> >Even when you upgrade the cygwin package and install it, it will ask you if
> >you would like to remove the old dll from the system32 folder. Then you
> >could just do a copy of the new one. That said you could just make a copy
>of
> >it to the folder where your executable is it will work there to. Thanks for
> >your time.
> >
> >                             Pharas
> >
> >-----Original Message-----
> >From: Larry Hall (RFK Partners, Inc) [mailto:lhall AT rfk DOT com]
> >Sent: Sunday, December 22, 2002 1:41 PM
> >To: Pharas; cygwin AT cygwin DOT com
> >Subject: RE: Running cygwin built programs in Windows XP
> >
> >Anyone who decides they want to do this is free to but it will invalidate
> >their installation and make it unstable.  Future problems they may run into
> >as a result will not be seriously entertained by this list (assuming said
> >persons post to this list for help in those cases) until cygwin1.dll is
> >put back where setup installed it.  For anyone wondering, copying
> >cygwin1.dll to this directory or any other carries the same warning.
> >
> >Larry Hall                              lhall AT rfk DOT com
> >RFK Partners, Inc.                      http://www.rfk.com
> >838 Washington Street                   (508) 893-9779 - RFK Office
> >Holliston, MA 01746                     (508) 893-9889 - FAX
> >
> >
> >At 12:55 AM 12/22/2002, Pharas wrote:
> > >Just stick cygwin1.dll in your windows\system32 folder.
> > >
> > >-----Original Message-----
> > >From: John Seeliger [mailto:jseelige AT aaahawk DOT com]
> > >Sent: Saturday, December 21, 2002 6:41 PM
> > >To: cygwin AT cygwin DOT com
> > >Subject: Running cygwin built programs in Windows XP
> > >
> > >How do I run a program that I built with gcc under Cygwin in Windows?
>When
> > >I try to run them, it says it can't find cygwin1.dll.
> > >
> > >--
> > >John Seeliger
>
>
>
>
>--
>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/


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