makeinfo with gdb.texinfo

makeinfo with gdb.texinfo

[Bob Rossi]

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

Re: makeinfo with gdb.texinfo

[Daniel Jacobowitz]

On Mon, Mar 31, 2003 at 12:22:11PM -0500, Bob Rossi wrote:
> 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.

Try running "make info" in a configured directory instead.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: makeinfo with gdb.texinfo

[Bob Rossi]

On Mon, Mar 31, 2003 at 12:42:22PM -0500, Daniel Jacobowitz wrote:
> On Mon, Mar 31, 2003 at 12:22:11PM -0500, Bob Rossi wrote:
> > 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.
> 
> Try running "make info" in a configured directory instead.
> 
> -- 
> Daniel Jacobowitz
> MontaVista Software                         Debian GNU/Linux Developer

That worked great. Thanks.

Does anyone know why I don't see the changed results I put into
gdb.texinfo when I do 'make info' in gdb.info?

The command 'make info' always update the gdb.info file when its
supposed to ( running makeinfo ). 
However when I view the file gdb.info using pinfo, I don't see the changes.

Also, when I grep for my changes, I see them in 
gdb.info-11, gdb.info-17 and gdb.texinfo.

Does this make any sense?

Thanks,
Bob Rossi

Re: makeinfo with gdb.texinfo

[Doug Evans]

Bob Rossi writes:
 > Does anyone know why I don't see the changed results I put into
 > gdb.texinfo when I do 'make info' in gdb.info?
 > 
 > The command 'make info' always update the gdb.info file when its
 > supposed to ( running makeinfo ). 
 > However when I view the file gdb.info using pinfo, I don't see the changes.
 > 
 > Also, when I grep for my changes, I see them in 
 > gdb.info-11, gdb.info-17 and gdb.texinfo.
 > 
 > Does this make any sense?

Yep.  If it's like the "info" command

bash$ info -f gdb.info

gives you the installed version whereas

bash$ info -f ./gdb.info

gives you the version in the current directory.

Re: makeinfo with gdb.texinfo

[Bob Rossi]

On Mon, Mar 31, 2003 at 10:12:44AM -0800, Doug Evans wrote:
> Bob Rossi writes:
>  > Does anyone know why I don't see the changed results I put into
>  > gdb.texinfo when I do 'make info' in gdb.info?
>  > 
>  > The command 'make info' always update the gdb.info file when its
>  > supposed to ( running makeinfo ). 
>  > However when I view the file gdb.info using pinfo, I don't see the changes.
>  > 
>  > Also, when I grep for my changes, I see them in 
>  > gdb.info-11, gdb.info-17 and gdb.texinfo.
>  > 
>  > Does this make any sense?
> 
> Yep.  If it's like the "info" command
> 
> bash$ info -f gdb.info
> 
> gives you the installed version whereas
> 
> bash$ info -f ./gdb.info
> 
> gives you the version in the current directory.

Thanks for the help. Thats exactly what the problem was.

Bob Rossi

Re: makeinfo with gdb.texinfo

[Ben Elliston]

Doug Evans <dje@transmeta.com> writes:

> Yep.  If it's like the "info" command
> bash$ info -f gdb.info
> gives you the installed version whereas
> bash$ info -f ./gdb.info
> gives you the version in the current directory.

It's annoying behaviour and, IMHO, a bug.  Shouldn't info use copies
in the local directory if they can be found, otherwise search the info
path?

Ben

Re: makeinfo with gdb.texinfo

[Eli Zaretskii]

> From: Ben Elliston <bje@wasabisystems.com>
> Date: 02 Apr 2003 09:48:40 +1000
> 
> > Yep.  If it's like the "info" command
> > bash$ info -f gdb.info
> > gives you the installed version whereas
> > bash$ info -f ./gdb.info
> > gives you the version in the current directory.
> 
> It's annoying behaviour and, IMHO, a bug.

Actually, it's a deliberately programmed feature.  It's even described
in the manual: relative file names are interpreted as being relative
to one of the directories mentioned in the INFOPATH environment
variable (or in the default Info search path if INFOPATH is
undefined).

> Shouldn't info use copies in the local directory if they can be
> found, otherwise search the info path?

It mimics the behavior of a Unix shell when searching for executable
programs: the current directory is never searched, unless you have "."
in your PATH.

Re: makeinfo with gdb.texinfo

[Ben Elliston]

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

Eli Zaretskii wrote:

>Actually, it's a deliberately programmed feature.  It's even described
>in the manual: relative file names are interpreted as being relative
>to one of the directories mentioned in the INFOPATH environment
>variable (or in the default Info search path if INFOPATH is
>undefined).
>
>It mimics the behavior of a Unix shell when searching for executable
>programs: the current directory is never searched, unless you have "."
>in your PATH.
>
One could argue that there is a fundamental difference between a shell 
and other programs: the shell executes programs; most others treat their 
arguments as input files.  In the context of a shell, it makes sense to 
apply a search path to prevent users from accidentally executing the 
wrong program.  You will note that it is not necessary to run `gdb 
./a.out' to debug a program of that name in the current working 
directory.  In the case of Info, the behaviour you describe creates, in 
practice, more problems than it solves.

Cheers, Ben

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3795 bytes --]

Re: makeinfo with gdb.texinfo

[Andreas Schwab]

Ben Elliston <bje@wasabisystems.com> writes:

|> Eli Zaretskii wrote:
|> 
|> >Actually, it's a deliberately programmed feature.  It's even described
|> >in the manual: relative file names are interpreted as being relative
|> >to one of the directories mentioned in the INFOPATH environment
|> >variable (or in the default Info search path if INFOPATH is
|> >undefined).
|> >
|> >It mimics the behavior of a Unix shell when searching for executable
|> >programs: the current directory is never searched, unless you have "."
|> >in your PATH.
|> >
|> One could argue that there is a fundamental difference between a shell and
|> other programs: the shell executes programs; most others treat their
|> arguments as input files.

But most other programs don't use a search path for their input files.
Compare with the C preprocessor, which distinguishes between <...> and
"...".

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: makeinfo with gdb.texinfo

[Andrew Cagney]

> One could argue that there is a fundamental difference between a shell and other programs: the shell executes programs; most others treat their arguments as input files.  In the context of a shell, it makes sense to apply a search path to prevent users from accidentally executing the wrong program.  You will note that it is not necessary to run `gdb ./a.out' to debug a program of that name in the current working directory.  In the case of Info, the behaviour you describe creates, in practice, more problems than it solves.

Um, it is acknwledged that GDB's behavior is confusing.  Something as 
simple as:

$ program
Segmentation fault
$ gdb program

can lead to GDB debugging the wrong program.  Hmm, security hole.

Andrew

Re: makeinfo with gdb.texinfo

[Eli Zaretskii]

> Date: Wed, 02 Apr 2003 21:46:13 +1000
> From: Ben Elliston <bje@wasabisystems.com>
>
> In the case of Info, the behaviour you describe creates, in 
> practice, more problems than it solves.

Obviously, I disagree, but you are welcome to post this on bug-texinfo
mailing list, where the Texinfo maintainers will see it.