From: Scott Garman <scott.a.garman@intel.com>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 3/4] docbook-utils-native: set SGML_EXTRA_CATALOGS in jw
Date: Fri, 18 Feb 2011 07:34:42 -0800 [thread overview]
Message-ID: <4D5E9192.20005@intel.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D306597332CC3082@shsmsx501.ccr.corp.intel.com>
On 02/17/2011 09:35 PM, Ke, Liping wrote:
> Hi, Scott
>
> I continuously meet below compile errors when I bitbake
> doc-utils-native today. I paste the log in the attachment, could you
> help to have a look. Thanks a lot for your help!
Hi Criping,
This looks like a problem I had fixed with the docbook-dsssl-stylesheets
package. I am going to guess that this was an incremental build as well?
These commands should clean out most of the suspect docbook-related
utilities:
bitbake docbook-utils-native -c cleanall
bitbake openjade-native -c cleanall
bitbake opensp-native -c cleanall
bitbake docbook-dsssl-stylesheets-native -c cleanall
Then do a bitbake docbook-utils-native and see if it builds this time.
Let me know how it goes.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-02-18 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 23:40 [PATCH 0/4] Urgent doc fixes for gtk+ Scott Garman
2011-02-17 23:40 ` [PATCH 1/4] docbook-dsssl-stylesheets-native: add missing files to install Scott Garman
2011-02-17 23:40 ` [PATCH 2/4] openjade-native: Set datadir explicitly Scott Garman
2011-02-17 23:40 ` [PATCH 3/4] docbook-utils-native: set SGML_EXTRA_CATALOGS in jw Scott Garman
2011-02-18 5:35 ` Ke, Liping
2011-02-18 15:34 ` Scott Garman [this message]
2011-02-17 23:40 ` [PATCH 4/4] gtk+: Fix build of documentation Scott Garman
2011-02-19 4:07 ` [PATCH 0/4] Urgent doc fixes for gtk+ Saul Wold
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=4D5E9192.20005@intel.com \
--to=scott.a.garman@intel.com \
--cc=liping.ke@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox