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 18:26:00 -0000 [thread overview] Message-ID: <20020514012603.31036.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 <jeff.deifik@jpl.nasa.gov> Cc: gcc-gnats@gcc.gnu.org Subject: Re: other/6653: make dvi fails on solaris, gcc-3.0.4 Date: Tue, 14 May 2002 02:22:12 +0100 (BST) On Mon, 13 May 2002, jeff deifik wrote: > TEXINPUTS=.:/home/jdeifik/work/gnu/jeff-native-gcc/gcc:/home/jdeifik/work/gnu/gc > c-3.0.4/gcc/doc::../../gcc-3.0.4/gcc/doc:../../gcc-3.0.4/gcc/doc/include: > INDEXSTYLE=.:/home/jdeifik/work/gnu/jeff-native-gcc/gcc:/home/jdeifik/work/gnu/g > cc-3.0.4/gcc/doc::../../gcc-3.0.4/gcc/doc:../../gcc-3.0.4/gcc/doc/include: > + test -n > + sed 1q ./../../gcc-3.0.4/gcc/doc/gcc.texi > + fgrep input texinfo > language=texinfo > bibtex= > texindex=texindex > + test dvi = dvi > tex=tex > + test = t > txiversion_tex=txiversion.tex > + echo \input texinfo.tex @bye > + cd /tmp/t2d5992 > + sed -n s/^.*\[\(.*\)version \(....\)-\(..\)-\(..\).*$/txiformat=\1 > txiversion= > "\2\3\4"/p > + tex txiversion.tex > + eval > + false texinfo.tex preloaded as `', version is `' ... > + test 19990129 -le OK, the problem appears to be that the test for texinfo.tex being recent enough for macro expansion is done in a temporary directory, but the TEXINPUTS setting (from the -I arguments) pointing to the right texinfo.tex to use still includes relative paths. Report this to the Texinfo maintainers as a Texinfo bug. As a workaround, install a sufficiently recent (at least 19990129) texinfo.tex version in a directory TeX searches by default, or set TEXINPUTS to point to such a directory before running texi2dvi; if macro support is detected, the right version of texinfo.tex (that included with GCC) will then be used for the actual formatting. -- Joseph S. Myers jsm28@cam.ac.uk
next reply other threads:[~2002-05-14 1:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-13 18:26 Joseph S. Myers [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-25 2:22 bangerth 2002-05-13 15:46 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=20020514012603.31036.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: 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).