From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] Build arm-elf-gdb on mingw host
Date: Sat, 08 Apr 2006 20:21:00 -0000 [thread overview]
Message-ID: <20060408202135.GA18478@nevyn.them.org> (raw)
In-Reply-To: <20050926142611.GA17967@trixie.casa.cgf.cx>
On Mon, Sep 26, 2005 at 10:26:11AM -0400, Christopher Faylor wrote:
> On Mon, Sep 26, 2005 at 10:14:36AM -0400, Daniel Jacobowitz wrote:
> >On Mon, Sep 26, 2005 at 10:08:41AM -0400, Christopher Faylor wrote:
> >>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.
> >
> >Ah, so the problem is that makeinfo fails to handle the '\r\n'?
> >Funny... I'd have expected an msys version of texinfo to expect \r\n.
>
> Ditto. I just checked and I didn't do this in earlier cygwin versions
> but I did rectify at this at some point this year so that texinfo now
> should be line-ending agnostic on cygwin.
Hi Chris,
Are you sure? I had this exact GDB build failure today; then I
staggered through a Cygwin upgrade (it tried to eat itself in
the postinstall scripts...) and tried again, same behavior. I'm using
Cygwin, no MSYS involved.
Sedding away the \r's in chew's output lets the build succeed.
This vaguely suggests that we ought to make chew only output \n's, for
compatibility...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-08 20:21 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 [this message]
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
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=20060408202135.GA18478@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.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