Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Patch to update gdbint.texinfo [01/04]
Date: Sat, 21 Mar 2009 14:39:00 -0000	[thread overview]
Message-ID: <1237637671.3044.121.camel@thomas> (raw)
In-Reply-To: <ud4cbp3s3.fsf@gnu.org>

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

On Sat, 2009-03-21 at 12:29 +0200, Eli Zaretskii wrote:
> > From: Jeremy Bennett <jeremy.bennett@embecosm.com>
> > Cc: gdb-patches@sourceware.org
> > Date: Sat, 21 Mar 2009 09:33:58 +0000
> > 
> > Thanks for doing this. Not sure what went wrong with the binaries. I
> > produced them on FC9 Linux, but only tested them on the same machine.
> > 
> > I've attached the PDF to this message. I will attach the PNG to a follow
> > up message.
> 
> Thanks, these images are OK.  Everything is committed now.  I tested
> only the text-mode Info output and verified that the Emacs Info reader
> shows the PNG image instead of the ASCII art.  If you can make sure
> that PDF and HTML output formats work as well, please do.
> 
> Btw, I think we also need an EPS format, for TeX and PS output.
> 

Hi Eli,

Thanks for all this. PDF and HTML output work fine.

I've attached the EPS format (compressed with bzip2) for use with
PostScript/DVI.

There seems to be a problem with PostScript and DVI output. "make dvi"
seems to create a PDF file (not a DVI file), then leading to an error.

        (/home/jeremy/partners/GDB/cvstrees/src/gdb/doc/fdl.texi Appendix I [436]
        [437] [438] [439] [440] [441] [442]) (Index) [443] [444] [445] [446] )
        (see the transcript file for additional information)</usr/share/texmf/fonts/typ
        e1/bluesky/cm/cmb10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmbx12.pfb></u
        sr/share/texmf/fonts/type1/bluesky/cm/cmbxti10.pfb></usr/share/texmf/fonts/type
        1/bluesky/cm/cmcsc10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb></u
        sr/share/texmf/fonts/type1/bluesky/cm/cmr7.pfb></usr/share/texmf/fonts/type1/bl
        uesky/cm/cmr8.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmr9.pfb></usr/share
        /texmf/fonts/type1/bluesky/cm/cmsl10.pfb></usr/share/texmf/fonts/type1/bluesky/
        cm/cmsl9.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmsltt10.pfb></usr/share/
        texmf/fonts/type1/bluesky/cm/cmss10.pfb></usr/share/texmf/fonts/type1/bluesky/c
        m/cmsy10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmsy9.pfb></usr/share/tex
        mf/fonts/type1/bluesky/cm/cmti10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/c
        mtt10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmtt12.pfb></usr/share/texmf
        /fonts/type1/bluesky/cm/cmtt9.pfb>
        Output written on gdb.pdf (451 pages, 1609029 bytes).
        Transcript written on gdb.log.
        /usr/bin/texi2dvi: no such file or directory: gdb.dvi
        make[2]: *** [gdb.dvi] Error 1
        make[2]: Leaving directory `/home/jeremy/partners/GDB/cvstrees/build/doc'
        make[1]: *** [subdir_do] Error 1
        make[1]: Leaving directory `/home/jeremy/partners/GDB/cvstrees/build'
        make: *** [dvi] Error 2

"make ps" doesn't work in the main directory. "make ps" in the "doc"
subdirectory gives the same behavior as "make dvi" above.

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.

I'll investigate further and raise a bug as appropriate.

ATB,


Jeremy

-- 
Tel:      +44 (1202) 416955
Cell:     +44 (7970) 676050
SkypeID: jeremybennett
Email:   jeremy.bennett@embecosm.com
Web:     www.embecosm.com


[-- Attachment #2: stack-frame.eps.bz2 --]
[-- Type: image/x-bzeps, Size: 48274 bytes --]

  reply	other threads:[~2009-03-21 12:14 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 [this message]
2009-03-21 15:58         ` Eli Zaretskii
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=1237637671.3044.121.camel@thomas \
    --to=jeremy.bennett@embecosm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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