Re: testing release-2011.03 failure

[Tom Rini <tom_rini@mentor.com>]

On 02/15/2011 10:25 AM, Gary Thomas wrote:
> On 02/15/2011 09:53 AM, Tom Rini wrote:
>> On 02/14/2011 04:33 PM, Gary Thomas wrote:
>>> MACHINE = beagleboard
>>> DISTRO = angstrom-2010.x
>>> PARALLEL_MAKE ?= "-j4"
>>> BB_NUMBER_THREADS ?= "4"
>>> target = angstrom-gnome-image
>>> bitbake = 1.11.0
>>> host = Fedora 13/x86
>>>
>>> openembedded/recipes/gnome/system-tools-backends_2.10.1.bb failed
>>>
>>> Log at http://pastebin.com/rL0BnD8w
>>
>> Can you try adding PARALLEL_MAKE = "" to the offending recipe?
>
> Still errors, but maybe more readable:
>
> | Making all in services
> | make[2]: Entering directory
> `/work/local/Angstrom_BeagleBoard/tmp/work/armv7a-angstrom-linux-gnueabi/system-tools-backends-2.10.1-r1/system-tools-backends-2.10.1/services'
>
> | cd .. && \
> | /bin/sh
> /work/local/Angstrom_BeagleBoard/tmp/work/armv7a-angstrom-linux-gnueabi/system-tools-backends-2.10.1-r1/system-tools-backends-2.10.1/missing
> --run automake-1.7 --gnu services/Makefile
> | configure.in:8: version mismatch. This is Automake 1.7.9,
> | configure.in:8: but the definition used by this AM_INIT_AUTOMAKE
> | configure.in:8: comes from Automake 1.11.1. You should recreate
> | configure.in:8: aclocal.m4 with aclocal and run automake again.
> | make[2]: *** [Makefile.in] Error 1
> | make[2]: Leaving directory
> `/work/local/Angstrom_BeagleBoard/tmp/work/armv7a-angstrom-linux-gnueabi/system-tools-backends-2.10.1-r1/system-tools-backends-2.10.1/services'
>
> | make[1]: *** [all-recursive] Error 1
> | make[1]: Leaving directory
> `/work/local/Angstrom_BeagleBoard/tmp/work/armv7a-angstrom-linux-gnueabi/system-tools-backends-2.10.1-r1/system-tools-backends-2.10.1'
>
> | make: *** [all] Error 2

OK, digging into the history on this recipe, it looks like 
29dc4e1f8452bba3af0ff91811d93bdb9f4f4f23 is when we switched from 
"pre-mangle configure.in, etc, then normal autotools.bbclass 
do_configure" to "less mangle, call out gnu-config, oe_runconf, etc by 
hand".  Koen, do you recall why?  And what heart burn we would run into 
if we wanted to both not re-break policykit support and fix this build 
issue by getting a more complete autotools.bbclass:do_configure type 
do_configure run here?

-- 
Tom Rini
Mentor Graphics Corporation