From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9531] NPM fails to build embedded modules
Date: Thu, 29 Dec 2016 23:50:58 +0000 [thread overview]
Message-ID: <bug-9531-163-WQbN0hopjc@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 #4 from bilge at scriptfusion.com ---
Further investigation reveals the culprit is the `-g` switch in the line,
`$(NPM) install -g $(NODEJS_MODULES_LIST)` in package/nodejs/nodejs.mk.
Removing the `-g` switch allows the module and all its dependencies, including
sqlite3, to build successfully. However, since they are now built in a
different location, they are not included in the rootfs which defeats the
purpose of building them!
My knowledge of Buildroot is too poor to know why an access denied violation
occurs with `-g` or how to include the modules in the rootfs when the `-g`
option is omitted, however I know the 2014.08 release of Buildroot did not rely
on `-g` and this is the last known release version I could get this module
working on.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-12-29 23:50 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 [this message]
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
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-WQbN0hopjc@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