public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cestrauss at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/45888] tm.texi generation is not portable, rule is broken Date: Wed, 24 Nov 2010 00:28:00 -0000 [thread overview] Message-ID: <bug-45888-4-pSufZ6Arsm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-45888-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45888 --- Comment #14 from Cesar Strauss <cestrauss at gmail dot com> 2010-11-24 00:00:00 UTC --- (In reply to comment #8) > Created attachment 22400 [details] > Proposed patch > > Does this patch work for you on Cygwin? > Dear Jorn, I tried your patch on MinGW, and it does solve the issue for me. The tm.texi file does not have CR anymore, allowing the build to proceed normally past this point. On Cygwin, the patch is not needed (but does no harm) because the default line end encoding on Cygwin is already LF. So, in the patch, I suggest replacing the comment "To make this work on Cygwin, remove \r." by "To make this work on MinGW, remove \r.". I do not know why your patch didn't work for Anh Vo, maybe the build directory was not clean from a previous build. In any case, the tests you asked for do run normally for me on both MinGW and Cygwin: $ echo -e '\r' |od -x 0000000 0a0d 0000002 $ echo -e '\r' |tr -d '\015'|od -x 0000000 000a 0000001 $ case `echo X|tr X '\101'` in \ > A) echo ascii;;\ > *) echo ebdic;;\ > esac ascii
next prev parent reply other threads:[~2010-11-24 0:01 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-05 5:30 [Bug bootstrap/45888] New: " rwild at gcc dot gnu.org 2010-10-05 8:33 ` [Bug bootstrap/45888] " schwab@linux-m68k.org 2010-10-05 18:19 ` fxcoudert at gcc dot gnu.org 2010-10-05 23:39 ` amylaar at gcc dot gnu.org 2010-10-05 23:59 ` joseph at codesourcery dot com 2010-10-07 4:57 ` rwild at gcc dot gnu.org 2010-10-07 8:03 ` amylaar at gcc dot gnu.org 2010-10-07 18:34 ` Ralf.Wildenhues at gmx dot de 2010-11-15 15:00 ` amylaar at gcc dot gnu.org 2010-11-15 15:46 ` amylaar at gcc dot gnu.org 2010-11-18 15:13 ` amylaar at gcc dot gnu.org 2010-11-19 15:57 ` rwild at gcc dot gnu.org 2010-11-20 0:16 ` anhvofrcaus at gmail dot com 2010-11-20 0:47 ` amylaar at gcc dot gnu.org 2010-11-20 1:31 ` anhvofrcaus at gmail dot com 2010-11-20 1:57 ` amylaar at gcc dot gnu.org 2010-11-24 0:28 ` cestrauss at gmail dot com [this message] 2010-11-25 8:17 ` amylaar at gcc dot gnu.org 2010-11-30 1:12 ` anhvofrcaus at gmail dot com 2010-11-30 7:35 ` Ralf.Wildenhues at gmx dot de 2010-11-30 17:20 ` anhvofrcaus at gmail dot com 2010-12-02 23:39 ` cestrauss at gmail dot com 2010-12-03 0:47 ` amylaar at gcc dot gnu.org 2010-12-03 17:46 ` anhvofrcaus at gmail dot com 2010-12-03 17:57 ` amylaar at gcc dot gnu.org 2010-12-03 18:08 ` anhvofrcaus at gmail dot com 2010-12-03 18:15 ` amylaar at gcc dot gnu.org 2010-12-03 21:36 ` amylaar at gcc dot gnu.org 2010-12-03 22:35 ` anhvofrcaus at gmail dot com 2010-12-03 23:24 ` anhvofrcaus at gmail dot com 2010-12-04 1:04 ` amylaar at gcc dot gnu.org 2010-12-07 17:13 ` anhvofrcaus at gmail dot com 2010-12-10 2:05 ` amylaar at gcc dot gnu.org 2010-12-11 0:54 ` anhvofrcaus at gmail dot com 2010-12-11 3:51 ` amylaar at gcc dot gnu.org
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=bug-45888-4-pSufZ6Arsm@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).