public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: kevinb@redhat.com
Cc: gdb@sources.redhat.com
Subject: `Breakpoint related warnings' has no Up field
Date: Wed, 15 Oct 2003 16:34:00 -0000	[thread overview]
Message-ID: <200310151634.h9FGYPJ5021653@duracef.shout.net> (raw)

Oops, 'make install' on gdb HEAD just died on me.
native i686-pc-linux-gnu, red hat 8.0, texinfo 4.2.

Looks like some new texinfo needs a little adjustment, that's all.

Michael C

  makeinfo --split-size=5000000 -I /berman/fsf/_today_/source/gdb/HEAD/src/gdb/doc/../../readline/doc -I /berman/fsf/_today_/source/gdb/HEAD/src/gdb/doc/../mi -I /berman/fsf/_today_/source/gdb/HEAD/src/gdb/doc \
	  -o gdb.info /berman/fsf/_today_/source/gdb/HEAD/src/gdb/doc/gdb.texinfo
  /berman/fsf/_today_/source/gdb/HEAD/src/gdb/doc/gdb.texinfo:3312: `Breakpoint related warnings' has no Up field.
  /berman/fsf/_today_/source/gdb/HEAD/src/gdb/doc/gdb.texinfo:3312: warning: unreferenced node `Breakpoint related warnings'.
  makeinfo: Removing output file `gdb.info' due to errors; use --force to preserve.
  make[3]: *** [gdb.info] Error 2
  make[3]: Leaving directory `/berman/fsf/_today_/berman/build/target/native/gdb/HEAD/gdb/doc'
  make[2]: *** [subdir_do] Error 1
  make[2]: Leaving directory `/berman/fsf/_today_/berman/build/target/native/gdb/HEAD/gdb'
  make[1]: *** [install-only] Error 2
  make[1]: Leaving directory `/berman/fsf/_today_/berman/build/target/native/gdb/HEAD/gdb'
  make: *** [install-gdb] Error 2

             reply	other threads:[~2003-10-15 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 16:34 Michael Elizabeth Chastain [this message]
2003-10-15 17:58 ` [PATCH] Fix " Kevin Buettner

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=200310151634.h9FGYPJ5021653@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@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).