Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: gdb@sources.redhat.com
Subject: makeinfo with gdb.texinfo
Date: Mon, 31 Mar 2003 17:22:00 -0000	[thread overview]
Message-ID: <20030331172211.GB10233@white> (raw)

Hi, 

I am trying to figure out what the correct way to build the documentation
is. I want to create an info file. From the research I have done online, 
it seems as if 'makeinfo gdb.texinfo' should be the correct command.

This is the output I get.

bob@black:~/cvs/src/gdb/doc$ makeinfo gdb.texinfo
gdb.texinfo:11: @include `gdb-cfg.texi': No such file or directory.
gdb.texinfo:18836: @include `rluser.texinfo': No such file or directory.
gdb.texinfo:18836: @include `inc-hist.texinfo': No such file or
directory.
./gdb.texinfo:18838: Next reference to nonexistent node `Command Line
Editing'.
./gdb.texinfo:18924: Prev reference to nonexistent node `Using History
Interactively'.
./gdb.texinfo:13609: Cross reference to nonexistent node `Command Line
Editing'.
./gdb.texinfo:154: Menu reference to nonexistent node `Using History
Interactively'.
./gdb.texinfo:153: Menu reference to nonexistent node `Command Line
Editing'.
makeinfo: Removing output file `/home/bob/cvs/src/gdb/doc/gdb.info' due
to errors; use --force to preserve.

When I do 'makeinfo --force gdb.texinfo' I get 

bob@black:~/cvs/src/gdb/doc$ makeinfo --force gdb.texinfo
gdb.texinfo:11: @include `gdb-cfg.texi': No such file or directory.
gdb.texinfo:18836: @include `rluser.texinfo': No such file or directory.
gdb.texinfo:18836: @include `inc-hist.texinfo': No such file or
directory.
./gdb.texinfo:18838: Next reference to nonexistent node `Command Line
Editing'.
./gdb.texinfo:18924: Prev reference to nonexistent node `Using History
Interactively'.
./gdb.texinfo:13609: Cross reference to nonexistent node `Command Line
Editing'.
./gdb.texinfo:154: Menu reference to nonexistent node `Using History
Interactively'.
./gdb.texinfo:153: Menu reference to nonexistent node `Command Line
Editing'.

This actually creates the gdb.info file. However, it seems that when I
change gdb.texinfo then run 'makeinfo --force gdb.texinfo' again,
I can not see the changes in gdb.info. Does anyone know why this is?

Should I have to use --force to get the changes?
Why doesn't the Makefile do anything in the doc directory?
Do I have to invoke configure in a certain way?

Here is the version of makeinfo

bob@black:~/cvs/src/gdb/doc$ makeinfo --version
makeinfo (GNU texinfo) 4.1

Copyright (C) 2002 Free Software Foundation, Inc.
There is NO warranty.  You may redistribute this software
under the terms of the GNU General Public License.
For more information about these matters, see the files named COPYING.

Any help would be appreciated. 

Thanks,
Bob Rossi


             reply	other threads:[~2003-03-31 17:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 17:22 Bob Rossi [this message]
2003-03-31 17:42 ` Daniel Jacobowitz
2003-03-31 17:52   ` Bob Rossi
2003-03-31 18:12     ` Doug Evans
2003-03-31 18:22       ` Bob Rossi
2003-04-02  1:00       ` Ben Elliston
2003-04-02  3:25         ` Eli Zaretskii
2003-04-02 11:46           ` Ben Elliston
2003-04-02 13:10             ` Andreas Schwab
2003-04-02 15:48             ` Andrew Cagney
2003-04-03  2:57             ` Eli Zaretskii

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=20030331172211.GB10233@white \
    --to=bob_rossi@cox.net \
    --cc=gdb@sources.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