From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8296] nodejs 0.12.7 - npm crashes (seg core dump)
Date: Tue, 1 Dec 2015 21:49:49 +0000 (UTC) [thread overview]
Message-ID: <20151201214949.4D94F80567@busybox.osuosl.org> (raw)
In-Reply-To: <bug-8296-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8296
--- Comment #2 from Martin <martin@barkynet.com> 2015-12-01 21:49:49 UTC ---
Created attachment 6236
--> https://bugs.busybox.net/attachment.cgi?id=6236
qemu_x86_64_npm_crash_defconfig
qemu_x86_64_npm_crash_defconfig is modified from qemu_x86_64_defconfig. It has
the C++ compiler added, node.js and npm for the target. Running npm on the
target will crash.
Set BR2_TOOLCHAIN_BUILDROOT_GLIBC=y to test using glibc where npm will work.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-12-01 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 17:13 [Buildroot] [Bug 8296] New: nodejs 0.12.7 - npm crashes (seg core dump) bugzilla at busybox.net
2015-12-01 21:41 ` [Buildroot] [Bug 8296] " bugzilla at busybox.net
2015-12-01 21:42 ` bugzilla at busybox.net
2015-12-01 21:49 ` bugzilla at busybox.net [this message]
2015-12-01 22:04 ` bugzilla at busybox.net
2015-12-01 23:02 ` Martin Bark
2015-12-02 8:12 ` Thomas Petazzoni
2015-12-02 21:50 ` Mike Frysinger
2015-12-02 20:00 ` bugzilla at busybox.net
2015-12-02 20:58 ` bugzilla at busybox.net
2015-12-02 21:51 ` bugzilla at busybox.net
2015-12-02 22:01 ` bugzilla at busybox.net
2015-12-14 15:40 ` bugzilla at busybox.net
2015-12-23 17:48 ` 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=20151201214949.4D94F80567@busybox.osuosl.org \
--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.