From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9531] NPM fails to build embedded modules
Date: Sat, 31 Dec 2016 15:42:06 +0000 [thread overview]
Message-ID: <bug-9531-163-zDw9zG402o@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9531-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9531
--- Comment #12 from Peter Korsgaard <jacmet@uclibc.org> ---
(In reply to bilge from comment #11)
Ok, but I would strongly suggest not building as root. Several packages behave
differently when built as root (E.G. your npm issues), and Buildroot is
specifically made to not require root permissions and be used from normal
users. E.G. from the manual:
Important: you can and should build everything as a normal user. There is no
need to be root to configure and use Buildroot. By running all commands as a
regular user, you protect your system against packages behaving badly during
compilation and installation.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-12-31 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 10:59 [Buildroot] [Bug 9531] New: NPM fails to build embedded modules bugzilla at busybox.net
2016-12-29 11:10 ` [Buildroot] [Bug 9531] " bugzilla at busybox.net
2016-12-29 13:26 ` bugzilla at busybox.net
2016-12-29 13:33 ` bugzilla at busybox.net
2016-12-29 23:50 ` bugzilla at busybox.net
2016-12-30 19:43 ` bugzilla at busybox.net
2016-12-31 2:31 ` bugzilla at busybox.net
2016-12-31 11:39 ` bugzilla at busybox.net
2016-12-31 11:54 ` bugzilla at busybox.net
2016-12-31 11:58 ` bugzilla at busybox.net
2016-12-31 14:19 ` bugzilla at busybox.net
2016-12-31 14:23 ` bugzilla at busybox.net
2016-12-31 15:42 ` bugzilla at busybox.net [this message]
2017-03-05 15:34 ` bugzilla at busybox.net
2017-03-05 15:38 ` 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-9531-163-zDw9zG402o@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