From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [patch] Build arm-elf-gdb on mingw host
Date: Mon, 10 Apr 2006 16:58:00 -0000 [thread overview]
Message-ID: <20060410165802.GA26458@nevyn.them.org> (raw)
In-Reply-To: <20060410165125.GA17747@trixie.casa.cgf.cx>
On Mon, Apr 10, 2006 at 12:51:25PM -0400, Christopher Faylor wrote:
> >> 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?
>
> That was six months ago. If I had to guess, I'd guess that I wasn't
> talking about a cygwin update since the cygwin \r\n handling hasn't
> changed in years, AFAIK. I was probably talking about a texinfo.
> Texinfo links with the cygwin automode.o file, which means that it
> should, by default, accept \r\n input and spit out \n.
Right - sorry, I realized you meant a Texinfo package update. As of
4.8-1, a MinGW chew (which produces \r\n) causes texinfo to choke, but
a Cygwin chew (which produces \n) does not.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-10 16:58 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 [this message]
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=20060410165802.GA26458@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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