http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45888
--- Comment #13 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org>
2010-11-20 01:31:12 UTC ---
(In reply to comment #12)
> (In reply to comment #11)
> > Does the generated tm.texi still have carriage return characters?
> > Or is there some other difference to the tm.texi in $(srcdir)/doc ?
>
> When opening tm.texi under Word, I see ΒΆ character at the end of the lines. It
> must be the carriage return.
I'm not sure - it's been ages since I had to use minicom on DOS for the lack
of a terminal program on Linux (There's been seyon since... ISPs... and ADSL.)
Do you have od installed under cygwin?
You could try
od -x tm.texi|less
to fine out what really is in there. Or you could use hexdump if you have
that, but not od.
[jo...@laria gcc]$ od -x tm.texi|head -5
0000000 6340 4320 706f 7279 6769 7468 2820 2943
0000020 3120 3839 2c38 3931 3938 312c 3939 2c32
0000040 3931 3339 312c 3939 2c34 3931 3539 312c
0000060 3939 2c36 3931 3739 312c 3939 2c38 3931
0000100 3939 322c 3030 2c30 3032 3130 0a2c 6340
Notice the penultimate byte pair in the last line above. 0a is newline.
carriage return would show up as 0d .
Assuming you actually have a carriage return there, I wonder where things
go wrong with the conversion.
On a Linux system, echo will not emit a carriage return by default, but
I can ask it to:
[amyl...@meolyon ~]$ echo -e '\r' |od -x
0000000 0a0d
0000002
You should be getting two carriage returns (0d) on cygwin with that command.
And then I can filter out the carriage return with the tr command used in
the makefile:
[amyl...@meolyon ~]$ echo -e '\r' |tr -d '\015'|od -x
0000000 000a
0000001
The case statement can also be tested separately:
[amyl...@meolyon ~]$ case `echo X|tr X '\101'` in \
> A) echo ascii;;\
> *) echo ebdic;;\
> esac
ascii
Could you cut & paste this into a bash shell under cygwin and report the
results?
echo -e '\r' |od -x
echo -e '\r' |tr -d '\015'|od -x
case `echo X|tr X '\101'` in \
A) echo ascii;;\
*) echo ebdic;;\
esac
