* [Buildroot] [Bug 9721] version 2017.02: no acceptable m4 could be found in $PATH
2017-03-10 9:59 [Buildroot] [Bug 9721] New: version 2017.02: no acceptable m4 could be found in $PATH bugzilla at busybox.net
@ 2017-03-10 10:02 ` bugzilla at busybox.net
2017-03-10 12:21 ` bugzilla at busybox.net
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla at busybox.net @ 2017-03-10 10:02 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=9721
louigi600 at yahoo.it changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |arm
Host| |x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Buildroot] [Bug 9721] version 2017.02: no acceptable m4 could be found in $PATH
2017-03-10 9:59 [Buildroot] [Bug 9721] New: version 2017.02: no acceptable m4 could be found in $PATH bugzilla at busybox.net
2017-03-10 10:02 ` [Buildroot] [Bug 9721] " bugzilla at busybox.net
@ 2017-03-10 12:21 ` bugzilla at busybox.net
2017-03-10 19:53 ` bugzilla at busybox.net
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla at busybox.net @ 2017-03-10 12:21 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=9721
--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
Can you check in output/build/host-libtool-2.4.6/config.log to see why the m4
check fails?
I'm using m4 1.4.18 here without issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Buildroot] [Bug 9721] version 2017.02: no acceptable m4 could be found in $PATH
2017-03-10 9:59 [Buildroot] [Bug 9721] New: version 2017.02: no acceptable m4 could be found in $PATH bugzilla at busybox.net
2017-03-10 10:02 ` [Buildroot] [Bug 9721] " 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
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla at busybox.net @ 2017-03-10 19:53 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=9721
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr
--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
host-libtool in Buildroot has a dependency on host-m4, so you should have
seen host-m4 build before host-libtool.
Can you verify this is the case?
Also, I see you are building as root. This is absolutely not necessary,
and it is greatly suggested that you do not do that. Furthermore, this
is known to cause build issues in some packages (at least nodejs is
impacted). Can you retry running as non-root?
Finally, I see that you are building in a sub-directory of /usr, which
has caused issues in the past. Can you try bulding in your user's home
instead?
In the meantime, I'll try a local build in a sub-dir os /usr to check
the issue has not resurfaced...
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Buildroot] [Bug 9721] version 2017.02: no acceptable m4 could be found in $PATH
2017-03-10 9:59 [Buildroot] [Bug 9721] New: version 2017.02: no acceptable m4 could be found in $PATH bugzilla at busybox.net
` (2 preceding siblings ...)
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
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla at busybox.net @ 2017-03-13 14:27 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=9721
--- Comment #3 from louigi600 at yahoo.it ---
I think solved that issue that may have been induced (not sure how exactly
maybe at some point it's looking in /proc/mounts) by working chroot without
/sys /proc mountd on the chroot env. Unfortunately I don't have the failing
logs anymore.
I've got it to compile now but I've other issues while using the built
xtoolchain.
I know it's not necessary to compile using root ... but appart from being
superuser, root is just like any other user on the system.
I've seen some unix systems where the user homes are un /usr/home so that would
be a subfolder of usr anyway ... that's another odd thing a folder is a folder
and why should I not be able to build this from any folder I like to choose on
my system ?
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Buildroot] [Bug 9721] version 2017.02: no acceptable m4 could be found in $PATH
2017-03-10 9:59 [Buildroot] [Bug 9721] New: version 2017.02: no acceptable m4 could be found in $PATH bugzilla at busybox.net
` (3 preceding siblings ...)
2017-03-13 14:27 ` bugzilla at busybox.net
@ 2017-03-13 15:17 ` bugzilla at busybox.net
4 siblings, 0 replies; 6+ messages in thread
From: bugzilla at busybox.net @ 2017-03-13 15:17 UTC (permalink / raw)
To: buildroot
https://bugs.busybox.net/show_bug.cgi?id=9721
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #4 from Yann E. MORIN <yann.morin.1998@free.fr> ---
> that may have been induced [...] by working chroot without /sys
> /proc mountd on the chroot env.
OK, so this was an environment problem. Closing the issue.
Thanks for the heads-up. :-)
> but appart from being superuser, root is just like any other user
> on the system.
And it is causing build isues when building nodejs, because nodejs'
buildsystem does not work correctly when running as root. This is a
fact and an issue we do have encountered.
> why should I not be able to build this from any folder I like to
> choose on my system?
Well, we try hard to make it work. However, we have had issues when
building in a sub-dir of /usr, because some packages' buildsystems
behave incorrectly in this case. That's not entirely Buikldroot's
fault, although it should work now.
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread