From 2966b4375c35c873ff229f1896174e4bdcf7c954 Mon Sep 17 00:00:00 2001 From: Geoffrey Noer Date: Wed, 30 Dec 1998 21:53:20 +0000 Subject: [PATCH] * i386/xm-cygwin.h: change DIR_SEPARATOR to forward slash. From-SVN: r24445 --- gcc/ChangeLog | 4 ++++ gcc/config/i386/xm-cygwin.h | 11 ++++++++--- 2 files changed, 12 insertions(+), 3 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 015af043b58..33d4c7d57f5 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +Wed Dec 30 22:50:13 1998 Geoffrey Noer + + * i386/xm-cygwin.h: change DIR_SEPARATOR to forward slash. + 1998-12-30 Andreas Schwab * loop.c (check_dbra_loop): While reversing the loop, if the diff --git a/gcc/config/i386/xm-cygwin.h b/gcc/config/i386/xm-cygwin.h index 67040fea7ce..4b166ebde75 100644 --- a/gcc/config/i386/xm-cygwin.h +++ b/gcc/config/i386/xm-cygwin.h @@ -27,11 +27,16 @@ Boston, MA 02111-1307, USA. */ #define HAVE_RINDEX 1 #define HAVE_INDEX 1 -/* Even though we support "/", allow "\" since everybody tests both. */ -#define DIR_SEPARATOR '\\' +/* 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 */ + allow both unix and win32 PATH syntax. */ #undef GET_ENV_PATH_LIST #define GET_ENV_PATH_LIST(VAR,NAME) \ do { \ -- 2.30.2