Poky Project Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Broken dependency behavior in master?
Date: Fri, 01 Apr 2011 11:49:13 -0700	[thread overview]
Message-ID: <4D961E29.4070807@intel.com> (raw)
In-Reply-To: <1301679250.24596.293.camel@rex>

On 04/01/2011 10:34 AM, Richard Purdie wrote:
> On Fri, 2011-04-01 at 08:23 -0700, Scott Garman wrote:
>> On 04/01/2011 04:31 AM, Richard Purdie wrote:
>>>> This makes me think something could be seriously broken in master when
>>>> it comes to handling build dependencies.
>>>>
>>>> I've verified that sgml-common-native is showing up as a build
>>>> dependency properly in the dependency explorer.
>>>
>>> I'm not convinced as its clear above that sgml-common-native is being
>>> built before docbook-dsssl-stylesheets-native do_configure runs.
>>
>> That was the case on the autobuilder. On my local development system, I
>> proved to myself without a doubt that sgml-common-native only got as far
>> as do_configure before the docbook-sgml-dtd-3.1-native error was
>> encountered.
>
> With or without sstate involvement?

I've reproduced this now, multiple times, using builds from scratch, 
including the fact that reverting that commit fixes the the problem for me.

> This looks like some kind of sstate issue but without logs this is near
> impossible to comment on. The logs you've pointed at don't show the
> problem you're describing.

Please grab what you need to from here:

http://www.zenlinux.com/dropbox/

> I don't think the problem is as simple as you're suggesting it is though
> as the core dependency resolution appears to be working (and has not
> changed in a long time). What perhaps isn't in something in the sstate
> task acceleration.

Sure, I'm not insisting that this is the cause - it was just my initial 
hunch. And your intuition is clearly better than mine when it comes to 
this, so I trust it.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center


  reply	other threads:[~2011-04-01 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01  0:23 Broken dependency behavior in master? Scott Garman
2011-04-01 11:31 ` Richard Purdie
2011-04-01 15:23   ` Scott Garman
2011-04-01 17:34     ` Richard Purdie
2011-04-01 18:49       ` Scott Garman [this message]
2011-04-04 16:32         ` Paul Eggleton
2011-04-04 17:03           ` Richard Purdie

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=4D961E29.4070807@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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