From: Eli Zaretskii <eliz@gnu.org>
To: jeremy.bennett@embecosm.com
Cc: gdb-patches@sourceware.org
Subject: Re: Patch to update gdbint.texinfo [01/04]
Date: Sat, 21 Mar 2009 15:58:00 -0000 [thread overview]
Message-ID: <u8wmzos8a.fsf@gnu.org> (raw)
In-Reply-To: <1237637671.3044.121.camel@thomas>
> From: Jeremy Bennett <jeremy.bennett@embecosm.com>
> Cc: gdb-patches@sourceware.org
> Date: Sat, 21 Mar 2009 12:14:31 +0000
>
> Thanks for all this. PDF and HTML output work fine.
Thanks for testing.
> I've attached the EPS format (compressed with bzip2) for use with
> PostScript/DVI.
Thanks, I committed it.
> The problem seems to be that texi2dvi is generating PDF. This seems to
> be GDB specific. It applies to each of the GDB manuals (gdb.texinfo,
> gdbint.texinfo etc), but not to texinfo manuals in other projects.
>
> It could be connected with the move to replace etex by a link to pdftex
> in recent Linuxes (I'm using FC9), which may require some modification
> to GDB's custom texinfo.tex.
Does it work if you replace GDB's texinfo.tex with the one that comes
with the Texinfo manual? Does it perhaps help to invoke texi2dvi with
the --dvi switch?
> I'll investigate further and raise a bug as appropriate.
Thanks, please do.
next prev parent reply other threads:[~2009-03-21 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 11:21 Jeremy Bennett
2009-03-21 9:34 ` Eli Zaretskii
2009-03-21 10:30 ` Jeremy Bennett
[not found] ` <1237628038.3044.105.camel@thomas>
2009-03-21 12:14 ` Eli Zaretskii
2009-03-21 14:39 ` Jeremy Bennett
2009-03-21 15:58 ` Eli Zaretskii [this message]
2009-03-21 17:33 ` Joseph S. Myers
2009-03-21 18:27 ` Eli Zaretskii
2009-03-21 20:21 ` Jeremy Bennett
2009-03-22 14:24 ` Eli Zaretskii
2009-04-21 12:38 ` Joseph S. Myers
2009-04-21 18:54 ` 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=u8wmzos8a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jeremy.bennett@embecosm.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