public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/50900] 'gmake pdf' fails in libiberty
Date: Fri, 28 Oct 2011 19:02:00 -0000 [thread overview]
Message-ID: <bug-50900-4-1gea4dGjg4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50900-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50900
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-10-28 19:02:20 UTC ---
On Fri, Oct 28, 2011 at 06:33:57PM +0000, schwab@linux-m68k.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50900
>
> --- Comment #3 from Andreas Schwab <schwab@linux-m68k.org> 2011-10-28 18:33:57 UTC ---
> That's not the one being used.
>
Well, the only other version that I have, which could be the
problem, was installed with teTeX
troutmask:kargl[208] more /usr/local/share/texmf/tex/texinfo/texinfo.tex
% texinfo.tex -- TeX macros to handle Texinfo files.
%
% Load plain if necessary, i.e., if running under initex.
\expandafter\ifx\csname fmtname\endcsname\relax\input plain\fi
%
\def\texinfoversion{2011-05-23.16}
I'm in the middle of a new bootstrap. I'll see if I can find
out more information in an hour or so.
next prev parent reply other threads:[~2011-10-28 19:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 15:42 [Bug other/50900] New: " kargl at gcc dot gnu.org
2011-10-28 17:30 ` [Bug other/50900] " schwab@linux-m68k.org
2011-10-28 18:23 ` sgk at troutmask dot apl.washington.edu
2011-10-28 18:34 ` schwab@linux-m68k.org
2011-10-28 19:02 ` sgk at troutmask dot apl.washington.edu [this message]
2011-10-28 20:16 ` schwab@linux-m68k.org
2011-10-28 20:34 ` sgk at troutmask dot apl.washington.edu
2011-10-28 22:19 ` karl at freefriends dot org
2011-10-28 22:51 ` sgk at troutmask dot apl.washington.edu
2011-10-28 22:54 ` karl at freefriends dot org
2011-10-28 23:19 ` sgk at troutmask dot apl.washington.edu
2011-10-28 23:25 ` karl at freefriends dot org
2013-11-25 1:06 ` kargl at gcc dot gnu.org
2013-11-25 16:15 ` joseph at codesourcery dot com
2013-11-25 16:24 ` sgk at troutmask dot apl.washington.edu
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-50900-4-1gea4dGjg4@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: 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).