Poky Project Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Broken dependency behavior in master?
Date: Thu, 31 Mar 2011 17:23:39 -0700	[thread overview]
Message-ID: <4D951B0B.3010503@intel.com> (raw)

Hi Paul,

Beth pointed me to a failure occurring on the autobuilder when building 
docbook-sgml-dtd-3.1-native using the latest master:

http://autobuilder.pokylinux.org:8010/builders/nightly-external/builds/88/steps/shell_3/logs/stdio

I am able to reproduce it on my development system. The problem occurs 
because sgml-common-native is not being fully built before 
docbook-sgml-dtd-3.1-native, even though it is listed in DEPENDS. I see 
log files only up to the do_configure step for sgml-common-native.

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.

...ok, looking at the recent commits in master, this one raised my 
suspicion:

http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=b4268c08c350a7928a0b1a041b04ffe5a44e77b4

I just tried reverting that and doing a new build, and the build 
completed successfully. Could you take a closer look at it?

Thanks,

Scott

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


             reply	other threads:[~2011-04-01  0:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01  0:23 Scott Garman [this message]
2011-04-01 11:31 ` Broken dependency behavior in master? Richard Purdie
2011-04-01 15:23   ` Scott Garman
2011-04-01 17:34     ` Richard Purdie
2011-04-01 18:49       ` Scott Garman
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=4D951B0B.3010503@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=paul.eggleton@linux.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