From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 679] New: Autoconf cannot find M4
Date: Thu, 22 Oct 2009 16:09:57 +0000 (UTC) [thread overview]
Message-ID: <bug-679-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=679
Host: 586
Target: 386
Summary: Autoconf cannot find M4
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: opalenzuela at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.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.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-10-22 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 16:09 bugzilla at busybox.net [this message]
2009-10-22 18:24 ` [Buildroot] [Bug 679] Autoconf cannot find M4 bugzilla at busybox.net
2009-10-24 14:00 ` bugzilla at busybox.net
2009-11-09 19:55 ` bugzilla at busybox.net
2009-12-06 19:07 ` bugzilla at busybox.net
2009-12-06 20:12 ` bugzilla at busybox.net
2009-12-06 20:29 ` bugzilla at busybox.net
2009-12-07 8:14 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-679-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.