Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Sanity check failed after glibc deletion (was: Re: [PATCH] glibc: deleted)
Date: Thu, 28 Jul 2011 11:07:08 +0100	[thread overview]
Message-ID: <1311847629.30326.428.camel@phil-desktop> (raw)
In-Reply-To: <CAGiJk9fwxUGUbb1Fwf731X+Ujz4RN_3OkXpGHcJq+ER_sYMRQQ@mail.gmail.com>

I'm not familiar with oebb.sh or its functionality.  But, from what
you're saying below it sounds as though it works something like
"git-am".  If I'm understanding correctly you used it to apply the glibc
deletion patch, and now you get this sanity failure (whereas you didn't
get it immediately before applying the patch).  Is that right?

I can't think of any reason why deleting the glibc recipes would cause
the 32-bit header check to start failing, and that error certainly isn't
happening for me.  If you revert the patch, does the failure go away?
Have you verified that you really do have gnu/stubs-32.h installed in
the appropriate place?

p.

On Thu, 2011-07-28 at 09:30 +0200, Samuel Stirtzel wrote:
> My current configuration was set up with the help of the Angstrom
> instructions [1], and I applied patches via the "oebb.sh update"
> command.
> Running Bitbake would show the following sanity error on any image / machine:
> 
> samuel@S-Linux:/var/oe-core/setup-scripts$ bitbake console-image
> ERROR:  Poky's config sanity checker detected a potential misconfiguration.
>     Either fix the cause of this error or at your own risk disable the
> checker (see sanity.conf).
>     Following is the list of potential problems / advisories:
> 
>     You have a 32-bit libc, but no 32-bit headers.  You must install
> the 32-bit libc headers.
> 
> ERROR: Execution of event handler 'check_sanity_eventhandler' failed
> 
> 
> For me it looks like an error with my configuration, but on the other
> side, before the update building images with bitbake worked.
> Well I don't know exactly if this is caused by the glibc deletion, but
> IMHO it seems very likely.
> Anyone else faced the same problem?
> 
> Help would be very appreciated.
> 
> Regards
> --Samuel
> 
> [1] http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-angstrom/tree/README
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core





  reply	other threads:[~2011-07-28 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28  7:30 Sanity check failed after glibc deletion (was: Re: [PATCH] glibc: deleted) Samuel Stirtzel
2011-07-28 10:07 ` Phil Blundell [this message]
2011-07-28 11:25   ` Samuel Stirtzel

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=1311847629.30326.428.camel@phil-desktop \
    --to=philb@gnu.org \
    --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