All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9721] version 2017.02: no acceptable m4 could be found in $PATH
Date: Mon, 13 Mar 2017 15:17:14 +0000	[thread overview]
Message-ID: <bug-9721-163-0rV7CTG8qt@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9721-163@https.bugs.busybox.net/>

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.

      parent reply	other threads:[~2017-03-13 15:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]

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-0rV7CTG8qt@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.