From: Eli Zaretskii <eliz@gnu.org>
To: Dave Murphy <wintermute2k4@ntlworld.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [patch] Build arm-elf-gdb on mingw host
Date: Mon, 26 Sep 2005 19:08:00 -0000 [thread overview]
Message-ID: <uoe6fk5q3.fsf@gnu.org> (raw)
In-Reply-To: <43377D19.7050505@ntlworld.com> (message from Dave Murphy on Mon, 26 Sep 2005 05:46:17 +0100)
> Date: Mon, 26 Sep 2005 05:46:17 +0100
> From: Dave Murphy <wintermute2k4@ntlworld.com>
> CC: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
>
> Sorry, I should have said that under mingw/msys files read in text mode
> have line endings converted. There are numerous places in chew.c where
> it checks for a newline character with expressions like "while (at (tos,
> idx) == '\n')", see skip_white_and_stars(src, idx),
> strip_trailing_newlines(), remove_noncomments (src, dst),
> outputdots(), courierize(), bulletize(), copy_past_newline (ptr, idx,
> dst), kill_bogus_lines(), indent(), skip_past_newline () and nextword
> (string, word). It seemed easier to just read the input files as binary
> and suppress the conversion rather than make all the code deal with the
> "/r/n" sequence.
Text-mode read conversion just removes \r from a \r\n pair, thus
doing exactly what you want.
Others suggested that you actually mean the problem is with makeinfo,
not with chew. The error messages you show us also seem to indicate
that this is the problem. Can you please confirm that this indeed is
the case?
prev parent reply other threads:[~2005-09-26 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 23:23 Dave Murphy
2005-09-26 3:46 ` Eli Zaretskii
2005-09-26 3:59 ` Daniel Jacobowitz
2005-09-26 4:46 ` Dave Murphy
2005-09-26 13:23 ` Daniel Jacobowitz
2005-09-26 14:09 ` Christopher Faylor
2005-09-26 14:14 ` Daniel Jacobowitz
2005-09-26 14:26 ` Christopher Faylor
2005-09-26 14:31 ` Daniel Jacobowitz
2005-09-26 15:41 ` Christopher Faylor
2005-09-26 19:18 ` Eli Zaretskii
2006-04-08 20:21 ` Daniel Jacobowitz
2006-04-10 16:51 ` Christopher Faylor
2006-04-10 16:58 ` Daniel Jacobowitz
2005-09-26 19:16 ` Eli Zaretskii
2005-09-27 2:02 ` Christopher Faylor
2005-09-26 19:13 ` Eli Zaretskii
2005-09-26 19:08 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uoe6fk5q3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=wintermute2k4@ntlworld.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox