linux-btrace.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "M. Edward (Ed) Borasky" <znmeb@cesmail.net>
To: linux-btrace@vger.kernel.org
Subject: Re: Missing pictures in "btt.pdf" when building from the git repo
Date: Mon, 12 Jan 2009 15:18:44 +0000	[thread overview]
Message-ID: <496B5F54.90306@cesmail.net> (raw)
In-Reply-To: <4969608E.9020400@cesmail.net>

Alan D. Brunelle wrote:
> M. Edward (Ed) Borasky wrote:
>> I've got an openSUSE 11.1 system with some of the later "factory"
>> software installed. I've downloaded "blktrace" from the Git repo with
>> "git clone". Everything seems to be building correctly, but the
>> "btt.pdf" file isn't getting the figures. The LaTeX processing is
>> generating errors. I've attached the log of the "make docs" step.
>>
>> I'm guessing that I have the wrong versions of some of the LaTeX tools.
>> Is anyone else having problems like this?
> 
> Hello Ed -
> 
> I'm not having any problems compiling the doc with LaTeX & DVIPDFM
> versions:
> 
> $ latex --version
> pdfTeX using libpoppler 3.141592-1.40.3-2.2 (Web2C 7.5.6)
> kpathsea version 3.5.6
> Copyright 2007 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
> Kpathsea is copyright 2007 Karl Berry and Olaf Weber.
> There is NO warranty.  Redistribution of this software is
> covered by the terms of both the pdfTeX using libpoppler copyright and
> the Lesser GNU General Public License.
> For more information about these matters, see the file
> named COPYING and the pdfTeX using libpoppler source.
> Primary author of pdfTeX using libpoppler: Peter Breitenlohner
> (eTeX)/Han The Thanh (pdfTeX).
> Kpathsea written by Karl Berry, Olaf Weber, and others.
> 
> Compiled with libpng 1.2.27; using libpng 1.2.27
> Compiled with zlib 1.2.3.3; using zlib 1.2.3.3
> Compiled with libpoppler version 3.00
> 
> $ dvipdfm --version
> 
> dvipdfm, version 0.13.2c, Copyright (C) 1998, 1999 by Mark A. Wicks
> 
> What versions are you running?
> 
> Regards,
> Alan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrace" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Apparently there was something broken in the versions I had. They are
newer that the standard ones from the openSUSE 11.1 repository. I
dropped back to the defaults and it worked. So I'm going to try to
reproduce it and file a bug on the openSUSE package ("texlive" -- they
install the whole bundle). The clue was that it was using "pdfTeXk" and
not "pdfTeX" to convert the TeX inputs to PDFs.
-- 
M. Edward (Ed) Borasky, FBG, AB, PTA, PGS, MS, MNLP, NST, ACMC(P), WOM

I've never met a happy clam. In fact, most of them were pretty steamed.

      parent reply	other threads:[~2009-01-12 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11  2:59 Missing pictures in "btt.pdf" when building from the git repo on M. Edward (Ed) Borasky
2009-01-12  9:38 ` Missing pictures in "btt.pdf" when building from the git repo Alan D. Brunelle
2009-01-12 15:18 ` M. Edward (Ed) Borasky [this message]

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=496B5F54.90306@cesmail.net \
    --to=znmeb@cesmail.net \
    --cc=linux-btrace@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).