From: Eli Zaretskii <eliz@gnu.org>
To: "John McCabe" <john@assen.demon.co.uk>
Cc: gdb@sourceware.org
Subject: Re: Documentation in texinfo format.
Date: Sat, 25 Aug 2007 10:06:00 -0000 [thread overview]
Message-ID: <uk5rkudwq.fsf@gnu.org> (raw)
In-Reply-To: <46CF50BC.4671.6A82D8@john.assen.demon.co.uk>
> From: "John McCabe" <john@assen.demon.co.uk>
> Date: Fri, 24 Aug 2007 21:42:20 +0100
>
> I have got the src module from cvs which seems to contain a lot of this
> stuff, but when I try to run texify gdb.texinfo it comes up with an error
> finding gdb-cfg.texi. I found a comment on usenet from Eli Z that you need
> to do a make info in order for that to be produced, but I have no Makefile
You do have Makefile, it's just called Makefile.in. So
make info -f Makefile.in srcdir=.
should do the trick for producing the Info files.
For PDF files, I believe you will need to say something like
make info -f Makefile.in srcdir=. pdfdir=.
You will also need to have a program installed called `pdftex'.
> and, with the software I have installed (things like MinGW, Msys etc) the
> configure script doesn't work either.
With the above tricks, you don't need to run the configure script just
to produce documentation.
Note that the URL pointed out by Joel, namely
http://www.sourceware.org/gdb/documentation/, already includes the PDF
versions of the GDB manuals, so if you need just that, you might as
well download and use it, instead of producing it yourself.
next prev parent reply other threads:[~2007-08-25 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 20:42 John McCabe
2007-08-24 20:46 ` Joel Brobecker
2007-08-24 21:49 ` John McCabe
2007-08-24 21:54 ` Joel Brobecker
2007-08-25 10:08 ` Eli Zaretskii
2007-08-25 0:12 ` Brian Dessent
2007-08-25 10:09 ` Eli Zaretskii
2007-08-25 10:06 ` Eli Zaretskii [this message]
2007-08-25 10:11 ` 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=uk5rkudwq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=john@assen.demon.co.uk \
/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