public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/6653: make dvi fails on solaris, gcc-3.0.4
Date: Mon, 13 May 2002 15:46:00 -0000	[thread overview]
Message-ID: <20020513224602.21928.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/6653; it has been noted by GNATS.

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <jeff.deifik@jpl.nasa.gov>
Cc: <gcc-gnats@gcc.gnu.org>,  <gcc-bugs@gcc.gnu.org>
Subject: Re: other/6653: make dvi fails on solaris, gcc-3.0.4
Date: Mon, 13 May 2002 23:44:51 +0100 (BST)

 On 13 May 2002 jeff.deifik@jpl.nasa.gov wrote:
 
 > texi2dvi -I ../../gcc-3.0.4/gcc/doc -I ../../gcc-3.0.4/gcc/doc/include ../../gc\
 > c-3.0.4/gcc/doc/gcc.texi^M
 > /home/jdeifik/work/gnu/gcc-3.0.4/gcc/doc/invoke.texi:159: Unknown command `gol'\
 > .^M
 > /home/jdeifik/work/gnu/gcc-3.0.4/gcc/doc/invoke.texi:165: Unknown command `gol'\
 > .^M
 > /home/jdeifik/work/gnu/gcc-3.0.4/gcc/doc/invoke.texi:166: Unknown command `gol'\
 > .^M
 > /home/jdeifik/work/gnu/gcc-3.0.4/gcc/doc/invoke.texi:167 ...
 > 
 > This goes on for many lines, as the '@gol' is used many
 > times in invoke.texi. 
 > This is with "This is TeX, Version 3.14159 (Web2C 7.2)"
 
 If this is a complete log, that indicates that texi2dvi is trying to use
 makeinfo to expand macros, rather than TeX - you need to investigate why.  
 @gol is defined in different ways for TeX and info because of differences
 between how the two implementations of macro expansion work; texi2dvi -e
 is unlikely to work.  The texinfo.tex included with GCC is sufficiently
 recent that texi2dvi should detect that it supports macro expansion.
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


             reply	other threads:[~2002-05-13 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13 15:46 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-25  2:22 bangerth
2002-05-13 18:26 Joseph S. Myers
2002-05-13 14:26 jeff.deifik

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=20020513224602.21928.qmail@sources.redhat.com \
    --to=jsm28@cam.ac.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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: 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).