From: Scott Garman <scott.a.garman@intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Prelink documentation system appears to be obsolete.
Date: Tue, 08 Feb 2011 16:35:48 -0800 [thread overview]
Message-ID: <4D51E164.4080509@intel.com> (raw)
From my attempts to get documentation building correctly for prelink,
it's becoming clear to me that the package's documentation system uses a
number of deprecated teTeX elements and needs updating at a "big
picture" level. From what I understand, TeXLive is the new hotness and
requires some migration.
In doc/prelink.tex, build errors lead me to suggest the following changes:
Change \usepackage{fancyheadings} to \usepackage{fancyhdr}:
http://us.generation-nt.com/bug-421071-ftbfs-latex-error-file-fancyheadings-sty-not-found-help-164921921.html
Change [make|print]glossary to [make|print]nomenclature:
http://pleasemakeanote.blogspot.com/2009/02/latex-undefined-control-sequence.html
Don't define \ifpdf manually, \usepackage{ifpdf}:
http://old.nabble.com/Package-ifpdf-error:-name-clash---%5Cifpdf-is-already-defined-td18730554.html
After resolving these issues, I still end up with a failure building the
docs - but this time there's no clear error message to give me clues on
what needs fixing. My gut feeing is that the migration process from
teTeX to TeXLive needs to be done by someone more familiar with it than I.
Until that happens (or I suddenly become a TeX guru), I'm currently
advising that we keep the workaround in the prelink recipe which
prevents documentation from being built. Then I can move on to
addressing documentation builds in other packages.
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
Intel Open Source Technology Center
next reply other threads:[~2011-02-09 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 0:35 Scott Garman [this message]
2011-02-09 2:12 ` Prelink documentation system appears to be obsolete Mark Hatle
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=4D51E164.4080509@intel.com \
--to=scott.a.garman@intel.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.