From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/2] nodejs: new package
Date: Sat, 25 Aug 2012 19:15:38 +0200 [thread overview]
Message-ID: <20120825191538.4f545a35@skate> (raw)
In-Reply-To: <1344827150-25067-3-git-send-email-net147@gmail.com>
Hello Jonathan,
Le Mon, 13 Aug 2012 13:05:50 +1000,
Jonathan Liu <net147@gmail.com> a ?crit :
> Signed-off-by: Jonathan Liu <net147@gmail.com>
> ---
> package/Config.in | 1 +
> package/nodejs/Config.in | 20 +++++++++++++++
> package/nodejs/nodejs.mk | 63 ++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 84 insertions(+)
> create mode 100644 package/nodejs/Config.in
> create mode 100644 package/nodejs/nodejs.mk
nodejs includes V8 for executing the JavaScript code, and V8 generates
machine code to provide good performances when executing JavaScript.
This means that V8 is architecture dependent: apparently, in deps/v8/,
only IA32, x86-64, ARM and MIPS are supported.
However, I don't understand how you select the target architecture or
how it is detected. Some comments in the configure script also seem to
imply that on ARM, only ARMv7 is supported by V8.
Have you checked this, or did you try only a x86->x86 build?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-08-25 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 3:05 [Buildroot] [PATCH v4 0/2] nodejs: new package Jonathan Liu
2012-08-13 3:05 ` [Buildroot] [PATCH v4 1/2] python: enable bz2 module for host build Jonathan Liu
2012-08-13 3:05 ` [Buildroot] [PATCH v4 2/2] nodejs: new package Jonathan Liu
2012-08-25 17:15 ` Thomas Petazzoni [this message]
2012-08-25 17:17 ` Thomas Petazzoni
2012-08-26 1:51 ` Jonathan Liu
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=20120825191538.4f545a35@skate \
--to=thomas.petazzoni@free-electrons.com \
--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