From: "Joseph S. Myers" <jsm@polyomino.org.uk>
To: Jonathan Lennox <lennox@cs.columbia.edu>
Cc: Mark Mitchell <mark@codesourcery.com>,
Bryce McKinlay <mckinlay@redhat.com>, "H. J. Lu" <hjl@lucon.org>,
gcc-patches@gcc.gnu.org
Subject: Re: Gcc mainline failed to build with texinfo 4.6
Date: Wed, 07 Jul 2004 19:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0407071910190.15132@digraph.polyomino.org.uk> (raw)
In-Reply-To: <16620.12978.913176.487704@cnr.cs.columbia.edu>
On Wed, 7 Jul 2004, Jonathan Lennox wrote:
> Would it work to just put the texinfo commands
>
> @unmacro comma
> @macro comma
> ,
> @end comma
>
> somewhere in the header of sourcebuild.texi? It seems like that should work
> both for <=4.6 and for 4.7, from my reading of the 4.6 texinfo manual.
Maybe. Given the warning in the manual
* It is not advisable to redefine any TeX primitive, plain, or
Texinfo command name as a macro. Unfortunately this is a very large
set of names, and the possible resulting errors are completely
random.
I think doing so is best avoided.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
next prev parent reply other threads:[~2004-07-07 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040705165035.GA14427@lucon.org>
2004-07-05 17:04 ` Joseph S. Myers
2004-07-05 20:26 ` Joseph S. Myers
2004-07-05 20:37 ` Diego Novillo
2004-07-05 20:35 ` Bryce McKinlay
2004-07-06 3:36 ` Mark Mitchell
[not found] ` <Pine.LNX.4.58.0407060803390.18244@digraph.polyomino.org.uk>
[not found] ` <40EAC350.9010300@codesourcery.com>
2004-07-06 23:45 ` Joseph S. Myers
2004-07-07 3:21 ` Mark Mitchell
2004-07-07 12:15 ` Gerald Pfeifer
2004-07-07 17:52 ` Jonathan Lennox
2004-07-07 19:31 ` Joseph S. Myers [this message]
2004-07-07 20:13 ` Daniel Jacobowitz
2004-07-07 20:16 ` Joseph S. Myers
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=Pine.LNX.4.58.0407071910190.15132@digraph.polyomino.org.uk \
--to=jsm@polyomino.org.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=lennox@cs.columbia.edu \
--cc=mark@codesourcery.com \
--cc=mckinlay@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).