Re: autoreconf: automake failed with exit status: 1 Was: [oe-commits] Constantin Musca : automake: upgrade to 1.12.3

[Constantin Musca <constantinx.musca@intel.com>]

On 09/05/2012 05:05 PM, Martin Jansa wrote:
> On Tue, Sep 04, 2012 at 11:51:04AM +0000, git@git.openembedded.org wrote:
>> Module: openembedded-core.git
>> Branch: master
>> Commit: 1110da87a2395e1d516f092553e6ed542bb34805
>> URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=1110da87a2395e1d516f092553e6ed542bb34805
>>
>> Author: Constantin Musca <constantinx.musca@intel.com>
>> Date:   Mon Sep  3 10:06:42 2012 +0300
>>
>> automake: upgrade to 1.12.3
>>
>> Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>>
>> ---
>>
>>   .../{automake_1.12.1.bb => automake_1.12.3.bb}     |    6 +++---
>>   1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/meta/recipes-devtools/automake/automake_1.12.1.bb b/meta/recipes-devtools/automake/automake_1.12.3.bb
>> similarity index 92%
>> rename from meta/recipes-devtools/automake/automake_1.12.1.bb
>> rename to meta/recipes-devtools/automake/automake_1.12.3.bb
>> index 700592c..25069d7 100644
> Has anyone seen errors like this?
>
> | autoreconf: running: automake --foreign --add-missing --copy --force-missing --warnings=cross
> | automake: warning: unknown warning category 'cross'
> | automake: warnings are treated as errors
> | automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
> | autoreconf: automake failed with exit status: 1
> | ERROR: autoreconf execution failed.
> | ERROR: Function failed: do_configure (see /OE/shr-core/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/foxtrotgps-1.1.0-r1/temp/log.do_configure.32412 for further information)
> NOTE: recipe foxtrotgps-1.1.0-r1: task do_configure: Failed
> ERROR: Task 886 (/OE/shr-core/meta-openembedded/meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.0.bb, do_configure) failed with exit code '1'
>
> Failed like this for first time today.. so I suspect it's caused by automake upgrade.
>
> Cheers,
>
>> --- a/meta/recipes-devtools/automake/automake_1.12.1.bb
>> +++ b/meta/recipes-devtools/automake/automake_1.12.3.bb
>> @@ -39,10 +39,10 @@ SRC_URI += "${PATHFIXPATCH} \
>>   	    file://python-libdir.patch \
>>               file://py-compile-compile-only-optimized-byte-code.patch"
>>   
>> -SRC_URI[md5sum] = "ec25c1855cacf47e4bdee76a776b96ba"
>> -SRC_URI[sha256sum] = "24bf1640679ba4a9cbe2d36422f39a81eced7f556b576a7a2ccfc70ca85a1e2f"
>> +SRC_URI[md5sum] = "d2af8484de94cdee16d89c50aaa1c729"
>> +SRC_URI[sha256sum] = "095ffaa3ac887d1eb3511bf13d7f1fc9ec0503c6a06aeae05c93730cdda9a5a0"
>>   
>> -PR = "r1"
>> +PR = "r0"
>>   
>>   do_install () {
>>       oe_runmake 'DESTDIR=${D}' install
>>
>>
>> _______________________________________________
>> Openembedded-commits mailing list
>> Openembedded-commits@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-commits
I have sent a patch ([PATCH] automake 1.12.3: fix warnings) that 
eliminates the warnings.

Cheers,
Constantin Musca