Re: Master stability update

[Koen Kooi <koen@dominion.thruhere.net>]

Op 27 jan 2011, om 16:35 heeft Koen Kooi het volgende geschreven:

> 
> Op 27 jan 2011, om 16:06 heeft Richard Purdie het volgende geschreven:
> 
>> On Thu, 2011-01-27 at 13:45 +0100, Koen Kooi wrote:
>>> Op 25 jan 2011, om 23:07 heeft Richard Purdie het volgende geschreven:
>>>> The following are know issues with master:
>>>> 
>>>> * Using rm_work and switching machines to machines of the same
>>>> "multimachine" architecture breaks.
>>>> 
>>>> * When switching machines of the same "multimachine" architecture (e.g.
>>>> emenlow to atom-pc), some sstate packages are changing checksums when at
>>>> first glance they shouldn't (e.g. perl do_install). A
>>> 
>>> After the fixes for those 2 went in builds from scratch fail with:
>>> 
>>> ERROR: Logfile of failure stored in: /OE/tentacle/build/tmp-angstrom_2010_x/work/x86_64-linux/gmp-native-5.0.1-r0/temp/log.do_configure.31887
>>> Log data follows:
>>> | automake (GNU automake) 1.9.6
>>> | Written by Tom Tromey <tromey@redhat.com>.
>>> |
>>> | Copyright 2005 Free Software Foundation, Inc.
>>> | This is free software; see the source for copying conditions.  There is NO
>>> | warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>>> | AUTOV is 1.9
>>> | NOTE: Executing autoreconf --verbose --install --force --exclude=autopoint -I /OE/tentacle/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/share/aclocal
>>> | /usr/bin/autoreconf2.50: unrecognized option `--exclude=autopoint'
>>> | Try `/usr/bin/autoreconf2.50 --help' for more information.
>>> | FATAL: autoreconf execution failed.
>>> | Function 'do_configure' failed (see /OE/tentacle/build/tmp-angstrom_2010_x/work/x86_64-linux/gmp-native-5.0.1-r0/temp/log.do_configure.31887 for further information)
>>> | ERROR: Function 'do_configure' failed (see /OE/tentacle/build/tmp-angstrom_2010_x/work/x86_64-linux/gmp-native-5.0.1-r0/temp/log.do_configure.31887 for further information)
>>> 
>>> It wants to use the autoreconf from my host, which doesn't have the `--exclude=autopoint' option since that's something OE patches in. After building autoconf native pseudo is gone!
>>> 
>>> /OE/tentacle/sources/openembedded/scripts/bitbake: line 38: /OE/tentacle/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/pseudo: No such file or directory
>>> 
>>> After building pseudo-native again:
>>> 
>>> NOTE: package pseudo-native-0.0+git0+bcb42d80c0817da5479ab9c4f2cd8c4727e98ef8-r17: task do_rm_work_all: Started
>>> NOTE: package pseudo-native-0.0+git0+bcb42d80c0817da5479ab9c4f2cd8c4727e98ef8-r17: task do_rm_work_all: Succeeded
>>> NOTE: Tasks Summary: Attempted 785 tasks of which 448 didn't need to be rerun and 0 failed.
>>> koen@dominion:/OE/tentacle$ MACHINE=beagleboard bitbake console-image
>>> /OE/tentacle/sources/openembedded/scripts/bitbake: line 38: /OE/tentacle/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/pseudo: No such file or directory
>> 
>> It seems that autoconf.bbclass change is having a weird ripple effect
>> with the sstate packages. Can you clean sstate and then retry, just to
>> try and isolate the issues?
>> 
>> I agree having a simple change to autotools.bbclass ripple through
>> sstate like that isn't desirable btw, I just want to try and fix one
>> issue at a time.
> 
> I removed tmp, sstate-cache and pseudodone, then did 'bitbake console-image', which failed at the same point. I looked into '/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/', which had a lot files in it, but no autoconf, so I did 'bitbake autoconf-native', that (re)ran a lot of rm_work tasks.
> 
> 
> koen@dominion:/OE/tentacle$ ls /OE/tentacle/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/
> tclConfig.sh*
> 
> so it removed pretty much everything from the sysroot!


RP said the following during a chat:

Its do_distribute_sources
That has triggered a new fetch call
and fetch triggered setscene
and setscene cleaned out the populate_staging

So we know what's going on, now figure out a fix :)