[OE-core] Sanity check failed after glibc deletion (was: Re: [PATCH] glibc: deleted)

[Samuel Stirtzel]

The oebb.sh script can be used to update all openembedded-core layers
and custom added sources from the layers.txt file in
"oe-core-dir/setup-scripts/sources/layers.txt".
After checking my local repositories with git-log again, I found out
that your patch is not responsible for this.
It seems like something else (most likely not openembedded-core
related) has caused this error.

My desktop PC runs a 64bit Linux.
After locating the error message in sanity.bbclass (line 279) which
follows, either (like you said) the stubs-32.h was removed or some
strange lib configurations applied something to my PC.
This could not be caused from updating the git repositories or
applying patches, so something else must have happened (I still wonder
what).
And since it occured right after i updated my sources my first guess
was glibc, I should have looked in the sanity.bbclass earlier.
--
if os.path.exists('%s/libc.so.6' % lib32path) and not
os.path.exists('/usr/include/gnu/stubs-32.h'):
          messages = messages + "You have a 32-bit libc, but no 32-bit
headers.  You must install the 32-bit libc headers.\n"
--
After I re-installed gcc-multilib the error disappeared.
Seems odd to me but the problems are gone.

Regards
--Samuel

2011/7/28 Phil Blundell <philb at gnu.org>:
> 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 at 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 at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>