From: Doug Evans <dje@transmeta.com>
To: Bob Rossi <bob_rossi@cox.net>
Cc: gdb@sources.redhat.com
Subject: Re: makeinfo with gdb.texinfo
Date: Mon, 31 Mar 2003 18:12:00 -0000 [thread overview]
Message-ID: <16008.34076.442297.792987@casey.transmeta.com> (raw)
In-Reply-To: <20030331175248.GC10233@white>
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.
next prev parent reply other threads:[~2003-03-31 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 17:22 Bob Rossi
2003-03-31 17:42 ` Daniel Jacobowitz
2003-03-31 17:52 ` Bob Rossi
2003-03-31 18:12 ` Doug Evans [this message]
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=16008.34076.442297.792987@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).