delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/06/13/18:23:10

X-Spam-Check-By: sourceware.org
From: "Charli Li" <KBarticle889459 AT aim DOT com>
To: "Cygwin Mailing List" <cygwin AT cygwin DOT com>
Subject: RE: PATHs in Windows and Cygwin
Date: Tue, 13 Jun 2006 18:24:43 -0400
Message-ID: <LLEBLEDLPAKFHFKGNDBMAEIHCBAA.KBarticle889459@aim.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <02c701c68ecd$36219c10$a501a8c0@CAM.ARTIMI.COM>
X-AOL-IP: 70.20.155.229
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

You have to set yourself up with a Windows batch script before you can even
start GNU programs.  Take the cygwin.bat in C:\cygwin for example  A simple
batch script like this:

@echo off

C:
set PATH=C:\cygwin\bin;%PATH%

cmd (or command if you're Windows 95/98/ME)

...would be able to locate the cygwin1.dll in C:\cygwin\bin.  That is what
Dave said about what's needed (cygwin1.dll) to run GNU applications.

----
ALSO
----
If the line containing cmd (command) is missing, the prompt would pop up for
a moment and then close.
----

Charli

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Dave Korn
> Sent: Tuesday, June 13, 2006 5:39 AM
> To: cygwin AT cygwin DOT com
> Subject: RE: PATHs in Windows and Cygwin
>
>
> On 13 June 2006 08:18, fergus wrote:
>
> > However, if I start Cygwin from a command prompt having first set the
> > Windows PATH to (null) as follows
> >
> >     c:> set PATH=
> >     c:> j:\bin\bash
> >
> > then not everything works: I get messages of the style "This
> application has
> > failed to start because cygwin1.dll was not found".
> >
> > 1. I realise that Cygwin is not standalone (it needs a Windows
> platform to
> > run) but I had not realised that the conduit to required
> Windows files would
> > be through PATH (if setting PATH to (null) is indeed the reason for the
> > error msgs and loss of functionality).
> >
> > But 2. If this _is_ the reason, why does the error msg refer to
> a missing
> > cygwin1.dll, which is clearly there on the Cygwin PATH?
> >
> > Can anybody illuminate this for me, please? Thank you.
>
>   It isn't possible to pull yourself up by your own bootstraps, basically!
> How could the cygwin dll be findable on the cygwin PATH unless it
> was already
> loaded in order to convert the cygwin POSIX path into win32 paths?
>
>   It's windows that is responsible for loading the cygwin dll, not cygwin.
> Hence it's the windows path that has to have cygwin's bin dir on it for
> cygwin1.dll to even be found before anything cygwin-ish (such as
> the cygwin
> PATH variable) even exists.
>
>
>     cheers,
>       DaveK
> --
> Can't think of a witty .sigline today....
>


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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019