From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2 v2] package/nodejs: fix architectural dependencies on ARM
Date: Mon, 19 Oct 2015 22:58:21 +0200 [thread overview]
Message-ID: <1445288301.1907.25.camel@embedded.rocks> (raw)
In-Reply-To: <03bfe81f7d32e7eb9b032d41d8c720d7ab95cb69.1445277033.git.yann.morin.1998@free.fr>
Hi Yann,
many thanks for working on this!
On Mo, 2015-10-19 at 19:51 +0200, Yann E. MORIN wrote:
> On ARM, starting with v0.12.x, the V8 JS engine is used, which now
> requires at least an armv6 and at least a VFPv2.
Nitpick, V8 is already used before 0.12.x. V8 dropped support for ARMv5
somewhere in between 0.10.x and 0.12.x.
> Since we're about to introduce the v4.x version, which has the same
> requirements, introduce an intermediate variable to hold that
> condition.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> ?package/nodejs/Config.in | 10 ++++++++--
> ?1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/package/nodejs/Config.in b/package/nodejs/Config.in
> index 329d270..bd63d29 100644
> --- a/package/nodejs/Config.in
> +++ b/package/nodejs/Config.in
> @@ -25,6 +25,13 @@ comment "nodejs needs a toolchain w/ C++, dynamic
> library, threads"
> ?
> ?if BR2_PACKAGE_NODEJS
> ?
> +# Starting with 0.12.x, on ARM, V8 (the JS engine)
> +# requires an armv6+ and a VFPv2+.
> +config BR2_PACKAGE_NODEJS_V8_ARCH_SUPPORTS
> + bool
> + default y
> + depends on !BR2_arm || !BR2_ARM_CPU_ARMV5 &&
> BR2_ARM_CPU_HAS_VFPV2
> +
> ?choice
> ? prompt "Node.js version"
> ? default BR2_BR2_PACKAGE_NODEJS_0_10_X if BR2_ARM_CPU_ARMV5
> @@ -35,10 +42,9 @@ choice
> ?config BR2_BR2_PACKAGE_NODEJS_0_10_X
> ? bool "v0.10.40"
> ?
> -# V8 included with v0.12.5 requires at least ARMv6
Maybe better: V8 included with 0.12.x does not support ARMv5?
> ?config BR2_BR2_PACKAGE_NODEJS_0_12_X
> ? bool "v0.12.7"
> - depends on !BR2_ARM_CPU_ARMV5
> + depends on BR2_PACKAGE_NODEJS_V8_ARCH_SUPPORTS
> ?
> ?endchoice
> ?
Best regards
J?rg Krause
next prev parent reply other threads:[~2015-10-19 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 17:50 [Buildroot] [PATCH 0/2 v2] package/nodejs: bump version (branch yem/node) Yann E. MORIN
2015-10-19 17:51 ` [Buildroot] [PATCH 1/2 v2] package/nodejs: fix architectural dependencies on ARM Yann E. MORIN
2015-10-19 20:27 ` Thomas Petazzoni
2015-10-19 20:30 ` Yann E. MORIN
2015-10-19 20:58 ` Jörg Krause [this message]
2015-10-19 21:10 ` Yann E. MORIN
2015-10-19 17:51 ` [Buildroot] [PATCH 2/2 v2] package/nodejs: add version 4.1.2 Yann E. MORIN
2015-10-19 20:30 ` Thomas Petazzoni
2015-10-19 20:35 ` Yann E. MORIN
2015-10-19 20:37 ` Thomas Petazzoni
2015-10-19 20:44 ` Yann E. MORIN
2015-10-19 21:31 ` Jörg Krause
2015-10-19 21:35 ` Yann E. MORIN
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=1445288301.1907.25.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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.