Bug 3610 - kconfig-frontends fails with newer autoconf
Summary: kconfig-frontends fails with newer autoconf
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.4
Hardware: All Multiple
: Medium critical
Target Milestone: 1.4 M2
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-12-16 18:13 UTC by Otavio Salvador
Modified: 2012-12-18 22:47 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
configure log (2.68 KB, application/octet-stream)
2012-12-16 18:13 UTC, Otavio Salvador 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Otavio Salvador 2012-12-16 18:13:41 UTC 
Created attachment 984 [details]
configure log

...
| configure.ac:27: error: possibly undefined macro: AS_IF
|       If this token and others are legitimate, please use m4_pattern_allow.
|       See the Autoconf documentation.
| configure.ac:100: error: possibly undefined macro: AC_MSG_ERROR
...

full log attached.
Comment 1 Saul Wold 2012-12-18 01:08:13 UTC 
A little more details would be helpful, like what git commit of master, which version of autoconf, arch building?  As you know we build world frequently on the Autobuilder and kconfig-frontends built over the weekend on the autobuilder.
Comment 2 Otavio Salvador 2012-12-18 11:28:08 UTC 
It was the HEAD of December 16; and the weird thing is that Martin had the same issue and a cleansstate fixed the issue for both of us.

Maybe a reentrance issue?
Comment 3 Saul Wold 2012-12-18 22:47:19 UTC 
I tried to run it twice via the bitbake -f -c configure and could not reproduce this issue, I am going to close this for now, if you can give me a reproducer then please reopen this bug.