All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M. Gregory" <mbgrego@tycho.nsa.gov>
To: meta-virtualization@yoctoproject.org
Subject: Re: stubs-32.h not found
Date: Tue, 2 Feb 2016 16:59:24 -0500	[thread overview]
Message-ID: <56B126BC.3070304@tycho.nsa.gov> (raw)
In-Reply-To: <56B10C90.8070709@tycho.nsa.gov>

On 02/02/2016 03:07 PM, M. Gregory wrote:
> I am working with the Xen recipes and I getting an odd behavior. The
> build will sometimes fail compiling Xen. The failure is a result of the
> absence of stubs-32.h (see error below). If I run a bitbake -c clean xen
> and build xen again everything builds as expected. According to the logs
> the do_stubs task runs and stubs-64.h is present in the sysroot, so
> stubs-32.h should have been created by the do_stubs task. I checked the
> timestamps on the do_populate_sysroot task of glibc and it was run after
> do_stubs, which indicates a dependence problem. I thought that adding
> glibc to the DEPENDS would fix the problem, but it did not. Any ideas? 
> -Machon
>
> fatal error: gnu/stubs-32.h: No such file or directory
>
So I read the Yocto manual and I understand why adding glibc to the
DEPENDS does not work. Specifically, DEPENDS only ensures "all the
dependencies listed have been built and have their contents in the
appropriate sysroots before the recipe's configure task is executed."
The do_stubs tasks running before configure. Adding the the line below
seems to fix the problem. Is this the correct solution?

Signed-off-by: Machon Gregory <mbgrego@tycho.nsa.gov>

diff --git a/recipes-extended/xen/xen.inc b/recipes-extended/xen/xen.inc
index 5555ed3..192bbee 100644
--- a/recipes-extended/xen/xen.inc
+++ b/recipes-extended/xen/xen.inc
@@ -783,6 +783,7 @@ do_stubs() {
 }

 addtask stubs after do_patch before do_configure
+do_stubs[depends] += "glibc:do_populate_sysroot"

 do_configure() {



  reply	other threads:[~2016-02-02 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 20:07 stubs-32.h not found M. Gregory
2016-02-02 21:59 ` M. Gregory [this message]
2016-02-04 20:52   ` Chris Patterson
2016-02-04 20:54     ` M. Gregory
2016-02-10 14:06       ` M. Gregory
2016-02-12 15:25         ` Chris Patterson

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=56B126BC.3070304@tycho.nsa.gov \
    --to=mbgrego@tycho.nsa.gov \
    --cc=meta-virtualization@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.