Mail Archives: djgpp-workers/1998/01/24/18:54:16
> > 7) #def DIR_SEPARATOR to '\' (from cygwin also)
> We had left it as '/' on purpose;
Whoops - Guess I didn't search back far enough in the mail archives
> gcc used to get confused about \
> after cpp was done with the file.
Hmm - as in stop compiling or not working at all at finding the file?
Thats definitely not the behaviour now.
> There was also a thread about \ vs
> / in the paths that gcc printed; it confused make again with $(system
> gcc --print-libgcc-location) or something.
I'll try this when I get back to work on manday.
> Since djgpp supports '/' fully, I'd recommend leaving it at that
> unless there's a compelling reason to change it.
The comments from the cygwin file seemed to indicate
that it would just enable '\' in addition to '/'. This change was
probably made after egcs split off so there is a chance its not
in the gcc sources. It would be 1 line near the bottom of the 'xm' file.
Should be easy to pull out if it causes the above mentioned problems
still.
- Raw text -