From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: sgml-common sstate_task_postfunc failure
Date: Mon, 25 Jun 2012 09:32:59 +0100 [thread overview]
Message-ID: <4FE8223B.3000105@communistcode.co.uk> (raw)
In-Reply-To: <4FE4A694.2040504@intel.com>
On 22/06/12 18:08, Scott Garman wrote:
> On 06/22/2012 01:50 AM, Jack Mitchell wrote:
>> I have had issues building sgml-common the past few days with oe-core
>> master. Could anyone shed any light on the debug messages I am receiving
>> and what I could do to go about fixing them.
>>
>> I don't really understand the recipe, it seems to be some sort of
>> surrogate recipe for transferring over specified files.
>
> The sgml catalog generation process has been plagued with race
> conditions and special cases like requiring SSTATEPOSTINSTFUNCS from
> the start - the problem is that unlike most packages, we're not
> installing static files but need to dynamically update the sgml
> catalog every time a new dtd gets installed.
>
> If this is reproducible, and you've only been experiencing it for the
> past few days, could you possibly bisect which commit has caused this
> error?
>
> Scott
>
>> snip...
>>
>
Unfortunately I had not updated or been building for around a month so
while reproducible on my current build I cannot say when over the last
month the issue turned up! I will keep updating and keep investigating
to see if I can come up with a suggestion.
I do have a quite a high parallel build at 12 threads, which has caused
problems in the past.
Regards,
Jack.
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2012-06-25 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 8:50 sgml-common sstate_task_postfunc failure Jack Mitchell
2012-06-22 17:08 ` Scott Garman
2012-06-25 8:32 ` Jack Mitchell [this message]
2012-06-26 12:41 ` Jack Mitchell
2012-06-26 12:53 ` Jack Mitchell
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=4FE8223B.3000105@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.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