From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9721] New: version 2017.02: no acceptable m4 could be found in $PATH
Date: Fri, 10 Mar 2017 09:59:52 +0000 [thread overview]
Message-ID: <bug-9721-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9721
Bug ID: 9721
Summary: version 2017.02: no acceptable m4 could be found in
$PATH
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: louigi600 at yahoo.it
CC: buildroot at uclibc.org
Target Milestone: ---
using buildroot on slackware 14.2_x86_64 I get this error:
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.16 or newer is recommended.
GNU M4 1.4.15 uses a buggy replacement strstr on some systems.
Glibc 2.9 - 2.12 and GNU M4 1.4.11 - 1.4.15 have another strstr bug.
package/pkg-generic.mk:206: recipe for target
'/usr/src/buildroot-2017.02/output/build/host-libtool-2.4.6/.stamp_configured'
failed
make: ***
[/usr/src/buildroot-2017.02/output/build/host-libtool-2.4.6/.stamp_configured]
Error 1
But I've m4 version 1.4.17 in path
root at desktopdbsm:/usr/src/buildroot-2017.02# echo $PATH
/usr/src/buildroot-2016.11.2/output/host/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/qt/bin:/usr/share/texmf/bin
root at desktopdbsm:/usr/src/buildroot-2017.02# type m4
m4 is /usr/bin/m4
root at desktopdbsm:/usr/src/buildroot-2017.02# m4 --version
m4 (GNU M4) 1.4.17
Copyright (C) 2013 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.
Written by Rene' Seindal.
root at desktopdbsm:/usr/src/buildroot-2017.02#
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-03-10 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:59 bugzilla at busybox.net [this message]
2017-03-10 10:02 ` [Buildroot] [Bug 9721] version 2017.02: no acceptable m4 could be found in $PATH bugzilla at busybox.net
2017-03-10 12:21 ` bugzilla at busybox.net
2017-03-10 19:53 ` bugzilla at busybox.net
2017-03-13 14:27 ` bugzilla at busybox.net
2017-03-13 15:17 ` 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-9721-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox