RE: Remaining host configuration fragments

[Bernard Dautrevaux <Dautrevaux at microprocess dot com>]

> -----Original Message-----
> From: DJ Delorie [mailto:dj@redhat.com]
> Sent: Monday, January 14, 2002 10:50 PM
> To: zack@codesourcery.com
> Cc: gcc@gcc.gnu.org
> Subject: Re: Remaining host configuration fragments
> 
> 
> 
> > In that case I wonder if it's appropriate to declare
> > HAVE_DOS_BASED_FILE_SYSTEM at all under cygwin.  GCC currently does
> > think it can get a drive letter in a pathname fed to it under
> > cygwin...
> 
> Cygwin will automagically alter $PATH (and a few others) to have
> posix-compliant unix-like paths, with ':' separators.  This is
> transparent to the application.
> 
> However, you can pass DOS paths to gcc *as parameters* like this:
> 
> 	C:\DOS> gcc c:\foo\bar.c
> 
> Cygwin will not change those for you.
> 
> So, colons in filenames are OK but colons in $PATH are separators.
> 

Note that there you call GCC from CMD.exe, so you should get a WINDOWS (i.e.
';' separated) PATH, not a cygwin one. However you can also have:

bash$ gcc c:\\foo\\bar.c

or

bash$ gcc c:/foo/bar.c

and in both cases you get a DOS-like filename argument (with drive letter)
while the PATH is ':'-separated; all this is a bit complicated ;-)

However the initial call (from CMD.exe) is not the standard way to invoke
gcc in the cygwin environment; it's rather the correct way to invoke a
mingw32-hosted gcc (and in that case all DOS conventions should be obeyed)
so cygwin-hosted gcc may well only expect a ':' separated PATH.

	Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
--------------------------------------------