From: Eli Zaretskii <eliz@gnu.org>
To: Dave Murphy <wintermute2k4@ntlworld.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Build arm-elf-gdb on mingw host
Date: Mon, 26 Sep 2005 19:13:00 -0000 [thread overview]
Message-ID: <umzlzk5ge.fsf@gnu.org> (raw)
In-Reply-To: <20050926140841.GB17370@trixie.casa.cgf.cx> (message from Christopher Faylor on Mon, 26 Sep 2005 10:08:41 -0400)
> Date: Mon, 26 Sep 2005 10:08:41 -0400
> From: Christopher Faylor <me@cgf.cx>
>
> I think I get it. This patch just modifies chew so that it always
> outputs '\n'. Then you see '\n' on input no matter what.
>
> Would it be possible to just link with binmode.o under mingw (and cygwin for
> that matter)?
If the problem is with MSYS's makeinfo, then it's IMHO wrong to solve
it in chew. Besides, the suggested change, viz
+#ifdef __MINGW32__
+/* Prevent \r\n\ line endings */
+#include <fcntl.h>
+unsigned int _CRT_fmode = _O_BINARY;
+#endif
is too general: it switches _all_ file I/O for _all_ files to binary
mode, in _all_ MinGW builds. Thus, if the file chew reads is edited
with some Windows editor that doesn't preserve line-endings (Emacs
does), then chew itself might fail.
Even if currently this change doesn't cause any trouble, it could be a
time bomb: imagine that at a later date someone adds code to chew that
reads some other file--we don't want to remember then to open it
explicitly in text mode to prevent bugs.
So I'm against this fix. If MSYS makeinfo is the culprit, let them
fix it, or let them use another port, which does TRT.
next prev parent reply other threads:[~2005-09-26 19:13 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 [this message]
2005-09-26 19:08 ` Eli Zaretskii
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=umzlzk5ge.fsf@gnu.org \
--to=eliz@gnu.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