From:	khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject:	Re: gcc --print-file-name: win32 or posix?
29 Dec 1998 16:52:48 -0800 :
Message-ID:	<199812300029.SAA27585.cygnus.cygwin32.developers@modi.xraylith.wisc.edu>
References:	<19981229153224 DOT 54748 AT cygnus DOT com>
To:	cygwin32-developers AT cygnus DOT com

Geoffrey Noer <noer AT cygnus DOT com> writes:
> FYI, I've submitted the following patch to the EGCS folks.  Now it
> continues to print Win32 paths but with forward slashes instead of
> backslashes.  This should make everything happy (configure and make
> seem to like the change at least...).

As long as we understand the caveat that GCC now will not accept 
paths like '-Ifoo\\bar' since most of the pathname logic uses the
following type of code:
  
  if (path[x] == '/' || path[x] == DIR_SEPARATOR)
   ...

I of course am quite happy to see this change, but thought I should
point this out. In fact, now that I think about, this is possibly
the better compromise than what I wanted to do -- completely removing 
support for non-POSIX paths (which included changing DIR_SEPARATOR
to '/' and also removing the definition for GET_ENV_PATH_LIST). 

With this change, the only possible complaint could be from folks
using the output of `gcc -print-search-dirs', expecting ':' as the 
path separator and getting ';' instead.

Regards,
Mumit

- Raw text -