From: noer AT cygnus DOT com (Geoffrey Noer)
Subject: Re: gcc --print-file-name: win32 or posix?
29 Dec 1998 16:04:00 -0800
Message-ID: <19981229153224.54748.cygnus.cygwin32.developers@cygnus.com>
References: <199812230227 DOT VAA02263 AT envy DOT delorie DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: cygwin32-developers AT cygnus DOT com

> If you do "gcc --print-file-name libgcc.a" cygwin's gcc currently
> prints the result using Win32 paths.  This breaks cygwin's make.  We
> were just about to change it to print posix paths, but we realized
> that it was done this way for a reason, and there are cases where it
> makes sense to print win32 paths.
[...]

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

-- 
Geoffrey Noer
noer AT cygnus DOT com

-------------------------> snip <-----------------------------

Tue Dec 29 15:13:38 1998  Geoffrey Noer  <noer AT cygnus DOT com>

	* i386/xm-cygwin.h: change DIR_SEPARATOR to forward slash.


Index: xm-cygwin.h
===================================================================
RCS file: /cvs/cvsfiles/devo/gcc/config/i386/xm-cygwin.h,v
retrieving revision 1.2
diff -c -p -r1.2 xm-cygwin.h
*** xm-cygwin.h	1998/11/24 01:09:17	1.2
--- xm-cygwin.h	1998/12/29 23:19:34
*************** Boston, MA 02111-1307, USA. */
*** 27,37 ****
  #define HAVE_RINDEX 1
  #define HAVE_INDEX 1
  
! /* Even though we support "/", allow "\" since everybody tests both.  */
! #define DIR_SEPARATOR '\\'
  
  /* If we allow both '/' and '\' as dir separators, then
!    allow both unix and win32 PATH syntax */
  #undef GET_ENV_PATH_LIST
  #define GET_ENV_PATH_LIST(VAR,NAME)					\
  do {									\
--- 27,42 ----
  #define HAVE_RINDEX 1
  #define HAVE_INDEX 1
  
! /* We support both "/" and "\" since everybody tests both but we
!    default to "/".  This is important because if gcc produces Win32
!    paths containing backslashes, make and configure may treat the
!    backslashes as escape characters.  Many Win32 programs use forward
!    slashes so using a forward slash shouldn't be problematic from the
!    perspective of wanting gcc to produce native Win32 paths. */
! #define DIR_SEPARATOR '/'
  
  /* If we allow both '/' and '\' as dir separators, then
!    allow both unix and win32 PATH syntax. */
  #undef GET_ENV_PATH_LIST
  #define GET_ENV_PATH_LIST(VAR,NAME)					\
  do {									\