Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Slater, Joseph" <joe.slater@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: libxslt populate_sysroot dependencies
Date: Wed, 09 Apr 2014 09:57:55 +0100	[thread overview]
Message-ID: <1397033875.24597.135.camel@ted> (raw)
In-Reply-To: <007BD92917A2324FA403BCF9A464CF8455D273D4@ALA-MBA.corp.ad.wrs.com>

On Tue, 2014-04-08 at 22:56 +0000, Slater, Joseph wrote:
> I've attached extracts from a very long log of a failure.  Turns out,
> it's not quite what I was expecting, but it does show the
> libxml2-native did not get to into sysroot before we tried to run
> xsltproc during the build of vala.
> 
> These failures are extremely rare, so I'll have to wait for another
> one to see if it's the same.  I realize that the build for libxml2
> seems to have "hung", but I also think that letting libxslt put itself
> into sysroot before what it needs to run is in there is dangerous.
> 
> Anyway, there's no way in the world I could do the number of builds
> necessary to see if it's still an issue with the current bitbake, so
> I'll just watch for more failures here.
> 
> This has been kind of a waste of your time.  Thanks for looking at it.

The question is whether in that build libxslt-native was in the DEPENDS
for vala-native or not?

Cheers,

Richard



      reply	other threads:[~2014-04-09  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 23:25 libxslt populate_sysroot dependencies Slater, Joseph
2014-04-08 16:57 ` Richard Purdie
2014-04-08 21:21   ` Slater, Joseph
2014-04-08 21:33     ` Richard Purdie
2014-04-08 22:56       ` Slater, Joseph
2014-04-09  8:57         ` Richard Purdie [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=1397033875.24597.135.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=joe.slater@windriver.com \
    --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