From: Jaap Crezee <jaap@jcz.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2 v3] package/nodejs: add version 4.1.2
Date: Sat, 21 Nov 2015 20:53:34 +0100 [thread overview]
Message-ID: <5650CBBE.4080604@jcz.nl> (raw)
In-Reply-To: <CAFGQKxeC83GJHc5+kHb3gJyyeXdSMJ6fFrSL8eRQXCjPVaHQ_A@mail.gmail.com>
Hi all,
Can somebody please add the following (might not be completely right, that's why I post it
like this):
[jaap at jaap /data/work/zupr/git/buildroot ]$ git diff
diff --git a/package/nodejs/Config.in b/package/nodejs/Config.in
index 5128901..8d0ecad 100644
--- a/package/nodejs/Config.in
+++ b/package/nodejs/Config.in
@@ -32,7 +32,7 @@ config BR2_PACKAGE_NODEJS_V8_ARCH_SUPPORTS
# On supported architectures other than ARM, no special requirement
default y if !BR2_arm
# On ARM, at least ARMv6+ with VFPv2+ is needed
- default y if !BR2_ARM_CPU_ARMV5 && BR2_ARM_CPU_HAS_VFPV2
+ default y if !BR2_ARM_CPU_ARMV5 && BR2_ARM_CPU_HAS_VFPV2 || BR2_ARM_CPU_HAS_NEON
choice
prompt "Node.js version"
[jaap at jaap /data/work/zupr/git/buildroot ]$
To my oppinion Neon is a VFPv2 succesor. NodeJS builds and runs fine with Neon selected
instead of VFPv2 for Cortex-A9.
Kind regards,
Jaap Crezee
next prev parent reply other threads:[~2015-11-21 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 21:59 [Buildroot] [PATCH 0/2 v3] package/nodejs: bump version (branch yem/node) Yann E. MORIN
2015-10-19 21:59 ` [Buildroot] [PATCH 1/2 v3] package/nodejs: fix architectural dependencies on ARM Yann E. MORIN
2015-10-19 21:59 ` [Buildroot] [PATCH 2/2 v3] package/nodejs: add version 4.1.2 Yann E. MORIN
2015-10-20 8:25 ` Martin Bark
2015-10-20 9:01 ` Richard Chapman
2015-10-20 16:25 ` Yann E. MORIN
2015-10-20 16:32 ` Martin Bark
2015-11-21 19:53 ` Jaap Crezee [this message]
2015-11-22 0:16 ` Arnout Vandecappelle
2015-11-22 12:42 ` Jaap Crezee
2015-11-22 21:28 ` Martin Bark
2015-10-20 8:02 ` [Buildroot] [PATCH 0/2 v3] package/nodejs: bump version (branch yem/node) Thomas Petazzoni
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=5650CBBE.4080604@jcz.nl \
--to=jaap@jcz.nl \
--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