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 09:50:55 +0000 [thread overview]
Message-ID: <bug-9526-163-NuhQw40DQ7@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 #21 from bilge at scriptfusion.com ---
Yeah, I'm sorry, you're right. It doesn't really matter what order they're
built as long as `env` is only need on the target. I got confused because of
the other bug (9531) where I thought I was being told `env` was also needed *on
the target* in order to build modules. However, I believe that bug is not
related to the `env` issue at all.
Regardless, this bug can be laid to rest, although I still feel a little bad
that no change will be made to avoid someone else encountering the same
problem, even if it's just a note in the documentation.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-12-31 9:50 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
2016-12-31 9:50 ` 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-9526-163-NuhQw40DQ7@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