From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9526] Embedded NPM fails to start with "no such file or directory" error
Date: Sat, 31 Dec 2016 08:15:24 +0000 [thread overview]
Message-ID: <bug-9526-163-h2QjzeZZnn@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9526-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9526
--- Comment #20 from Peter Korsgaard <jacmet@uclibc.org> ---
(In reply to bilge from comment #19)
I think we are talking past eachother. Dependencies for on the target (E.G. the
thing that will finally do something with the rootfs) are all runtime
dependencies, so the build order doesn't matter.
So yeah, you simply need to enable busybox as well to make sure /usr/bin/env is
also available in the rootfs when the target needs it at runtime. You can tweak
the busybox config if you want to save some space, but you need to be careful
to not remove stuff that is needed elsewhere (E.G. env)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-12-31 8:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 10:46 [Buildroot] [Bug 9526] New: Embedded NPM fails to start with "no such file or directory" error bugzilla at busybox.net
2016-12-29 10:50 ` [Buildroot] [Bug 9526] " bugzilla at busybox.net
2016-12-29 13:24 ` bugzilla at busybox.net
2016-12-29 13:37 ` bugzilla at busybox.net
2016-12-29 14:25 ` bugzilla at busybox.net
2016-12-29 14:33 ` bugzilla at busybox.net
2016-12-29 16:13 ` bugzilla at busybox.net
2016-12-29 17:14 ` bugzilla at busybox.net
2016-12-29 17:17 ` bugzilla at busybox.net
2016-12-29 18:19 ` bugzilla at busybox.net
2016-12-30 7:35 ` bugzilla at busybox.net
2016-12-30 7:36 ` bugzilla at busybox.net
2016-12-30 10:31 ` bugzilla at busybox.net
2016-12-30 16:51 ` bugzilla at busybox.net
2016-12-30 20:50 ` bugzilla at busybox.net
2016-12-30 21:13 ` bugzilla at busybox.net
2016-12-30 21:17 ` bugzilla at busybox.net
2016-12-30 21:42 ` bugzilla at busybox.net
2016-12-30 21:50 ` bugzilla at busybox.net
2016-12-31 2:08 ` bugzilla at busybox.net
2016-12-31 8:15 ` bugzilla at busybox.net [this message]
2016-12-31 9:50 ` 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-9526-163-h2QjzeZZnn@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