public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/50900] New: 'gmake pdf' fails in libiberty
Date: Fri, 28 Oct 2011 15:42:00 -0000 [thread overview]
Message-ID: <bug-50900-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50900
Bug #: 50900
Summary: 'gmake pdf' fails in libiberty
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: other
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: kargl@gcc.gnu.org
Underfull \hbox (badness 10000) in paragraph at lines 669--673
[]@textrm For ex-am-ple, if @textsl bin[]prefix @textrm is @texttt /alpha/beta
/gamma/gcc/delta[]@textrm , @textsl pre-fix @textrm is
[22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35])
Appendix A [36] (/home/sgk/gcc/gcc4x/libiberty/copying-lib.texi [37] [38]
[39] [40] [41] [42]
/home/sgk/gcc/gcc4x/libiberty/copying-lib.texi:480: This command can appear onl
y outside of any environment, not in environment @enumerate.
@badenverr ...temp , not @inenvironment @thisenv }
@checkenv ...@ifx @thisenv @temp @else @badenverr
@fi
@sectionheading #1#2#3#4->{@checkenv {}
@csname #2fonts@endcsname @rmisbold @...
@\heading ...tionheading {#1}{sec}{Yomitfromtoc}{}
@suppressfirstparagraphin...
l.480 @heading NO WARRANTY
? q
OK, entering @batchmode/usr/local/bin/texi2dvi: pdfetex exited with bad status,
quitting.
gmake[2]: *** [libiberty.pdf] Error 1
gmake[2]: Leaving directory `/usr/home/sgk/gcc/obj4x/libiberty'
gmake[1]: *** [pdf-libiberty] Error 1
gmake[1]: Leaving directory `/usr/home/sgk/gcc/obj4x'
gmake: *** [do-pdf] Error 2
next reply other threads:[~2011-10-28 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 15:42 kargl at gcc dot gnu.org [this message]
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
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@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).