This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Build arm-elf-gdb on mingw host
- From: Daniel Jacobowitz <drow at false dot org>
- To: gdb-patches at sources dot redhat dot com
- Date: Sat, 8 Apr 2006 16:21:35 -0400
- Subject: Re: [patch] Build arm-elf-gdb on mingw host
- References: <4337317B.3050300@ntlworld.com> <uslvsjxtp.fsf@gnu.org> <20050926035937.GA24565@nevyn.them.org> <43377D19.7050505@ntlworld.com> <20050926132325.GA1219@nevyn.them.org> <20050926140841.GB17370@trixie.casa.cgf.cx> <20050926141436.GA2527@nevyn.them.org> <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