Bug 4826 - [Autobuilder] lib32-gcc requires autoconf 2.64 instead of 2.69
Summary: [Autobuilder] lib32-gcc requires autoconf 2.64 instead of 2.69
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-07-08 13:58 UTC by Ioana Grigoropol
Modified: 2013-08-20 20:00 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
log world (2.03 MB, application/octet-stream)
2013-07-08 13:58 UTC, Ioana Grigoropol
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ioana Grigoropol 2013-07-08 13:58:44 UTC
Created attachment 1316 [details]
log world

World build failed with message:

ERROR: Function failed: do_configure (log file is located at /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/build/tmp/work/x86-pokymllib32-linux/lib32-gcc/4.8.1-r0/temp/log.do_configure.7129)
ERROR: Logfile of failure stored in: /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/build/tmp/work/x86-pokymllib32-linux/lib32-gcc/4.8.1-r0/temp/log.do_configure.7129
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common']
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function gcc_multilib_setup
| DEBUG: Python function gcc_multilib_setup finished
| DEBUG: Executing shell function do_configure
| configure.ac:34: error: Please use exactly Autoconf 2.64 instead of 2.69.
| config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
Comment 1 Saul Wold 2013-08-20 20:00:48 UTC
I have not seen this issue come up again, I wonder if it was a tranisent (the 
worst type of bugs in my mind).  I tested it locally, I could could not 
reproduce it, I also tested it on the autobuilder and could not reproduce.  If 
we can get a reproducer, then we can re-open.