From: cgf AT cygnus DOT com (Christopher Faylor) Subject: Re: gcc --print-file-name: win32 or posix? 23 Dec 1998 22:13:12 -0800 Message-ID: <19981224004901.A28746.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: Geoffrey Noer , Mumit Khan Cc: DJ Delorie , cygwin32-developers AT cygnus DOT com On Wed, Dec 23, 1998 at 09:05:13PM -0800, Geoffrey Noer wrote: >On Wed, Dec 23, 1998 at 04:07:07PM -0600, Mumit Khan wrote: >> Can you tell us why it was done? I've asked this in the past, but never >> did get an answer. > >Sorry, it's all my fault! :-) > >I believe I made the change in gcc to make it output backslashes in >filenames a couple of years ago (?). This was intended to make gcc's >output look more Win32-native. And it did but in retrospect, it broke >more things than it fixed so I believe we should revert the change. >I've already done this locally and didn't see anything go wrong. >In fact, now configure recognizes ld as GNU ld again so it seem so >make things better if anything. I think we should get the gcc team to >commit the change back to forward slashes... Does it use forward slashes when it is a mingw-gcc, too? Or is this only under cygwin? cgf