From: Scott Garman <scott.a.garman@intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Cc: Yocto Project Discussions <yocto@linux.intel.com>
Subject: Bugs with new documentation recipes.
Date: Thu, 03 Feb 2011 16:07:15 -0800 [thread overview]
Message-ID: <4D4B4333.4080005@intel.com> (raw)
Hello,
Saul is currently reverting a few of my recent commits to master which
enabled a number of documentation infrastructure-related recipes
(docbook-utils in particular).
This will help to un-break the builds of a few packages - prelink,
iputils, and gtk+. However, if you've built the broken version of these
recipes you will need to delete the following from your native sysroot:
rm -rf etc/sgml
rm -rf usr/share/sgml
And then to clean up your package cache be sure to bitbake -c cleanall on:
docbook-utils-native
openjade-native
opensp-native
docbook-dsssl-stylesheets-native
docbook-sgml-dtd-3.1-native
sgml-common-native
I apologize for the trouble; I did not test these recipe additions in
the right environment (it was on a host system that had many of these
utilities installed already, which gave me false positives).
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
Intel Open Source Technology Center
reply other threads:[~2011-02-04 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D4B4333.4080005@intel.com \
--to=scott.a.garman@intel.com \
--cc=poky@yoctoproject.org \
--cc=yocto@linux.intel.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