| Summary: | Autoconf cannot find M4 | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Oriol <opalenzuela> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | buildroot, joshuazarr, noel.vellemans, peter.stosz |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | 586 | Target: | 386 |
| Build: | |||
|
Description
Oriol
2009-10-22 16:09:55 UTC
(In reply to comment #0) > There is a m4 installed in my platform (Ubuntu) with the version, while there > is one installed in the system: > > checking for GNU M4 that supports accurate traces... configure: error: no > acceptable m4 could be found in $PATH. > GNU M4 1.4.6 or later is required; 1.4.13 is recommended > > # m4 --version > m4 (GNU M4) 1.4.11 > Copyright (C) 2008 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Is this related to http://lists.busybox.net/pipermail/buildroot/2009-October/029957.html or http://lists.busybox.net/pipermail/buildroot/2009-October/029964.html? In other words, is this autoconf for the target or for the host? In any case, you'll need to provide more info - What is your .config, and what make target is failing? (In reply to comment #1) > (In reply to comment #0) > > There is a m4 installed in my platform (Ubuntu) with the version, while there > > is one installed in the system: > > > > checking for GNU M4 that supports accurate traces... configure: error: no > > acceptable m4 could be found in $PATH. > > GNU M4 1.4.6 or later is required; 1.4.13 is recommended > > > > # m4 --version > > m4 (GNU M4) 1.4.11 > > Copyright (C) 2008 Free Software Foundation, Inc. > > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > > This is free software: you are free to change and redistribute it. > > There is NO WARRANTY, to the extent permitted by law. > > > > Is this related to > http://lists.busybox.net/pipermail/buildroot/2009-October/029957.html or > http://lists.busybox.net/pipermail/buildroot/2009-October/029964.html? > > In other words, is this autoconf for the target or for the host? In any case, > you'll need to provide more info - What is your .config, and what make target > is failing? > I encountered the same bug, as also described here http://lists.busybox.net/pipermail/buildroot/2009-October/029964.html I modified /buildroot/package/autoconf and reverted to 2.63 (from 2.64) and the problem was resolved. -Joshua Zarr *** Bug 697 has been marked as a duplicate of this bug. *** There has been two commits related to this recently added to git: 9d998ad1d79ffb6f878a55c8f2ed60fe7e973f34 and 4fe7607b469716e7c27dc3ab7dca9e1a8d417934 Could you give current git a try and see if you still experience the problem? Thanks. Same issue with BR2009.08, working now with BR2009.11. (In reply to comment #5) > Same issue with BR2009.08, working now with BR2009.11. Please try latest git (or latest snapshot if git access is an issue) - The latest autoconf changes are post-2009.11. > I can CONFIRM that : > A) 2009.11 is comipling/building FINE ! > B) Latest GIT (today 20091207) is also working . > > with the shell "sh -> dash" (before this failed). Great, closing then. |