Problem building on BeOS...
candiazoo at comcast.net
Fri Jan 2 19:50:56 CET 2004
Hmm. I got the sources directly from sourceforge. I am thinking maybe the
lines are terminated with \r. I think there may be a line termination changing
program somewhere on BeBits... I'll go check!
In message <bt4afp$rgo$03$1 at news.t-online.com>, "Martin_v._Löwis" wrote:
> Zoo Keeper wrote:
> > For some reason, the Python preprocessing balks on the "\" line
> > character. Any ideas/thoughts? Is it just that my version of gcc is not
> > supported?
> Yes, in combination with the way your source files are structured.
> It appears that the line ending convention differs in your source files
> from the line endings that gcc expects. E.g. the source files may have
> \r\n at the end of a line, whereas your gcc may expect only \n. As
> a result, \\\r\n is treated as an escaped \r, which gives a stray \.
> I don't know what line ending convention your system uses, or where
> you got the sources from, but it appears you need to convert them.
> Later versions of gcc support "universal text mode".
More information about the Python-list