From: Jonathan Liu <net147@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/2] nodejs: new package
Date: Sun, 26 Aug 2012 11:51:07 +1000 [thread overview]
Message-ID: <5039810B.7090200@gmail.com> (raw)
In-Reply-To: <20120825191538.4f545a35@skate>
Hi Thomas,
On 26/08/2012 3:15 AM, Thomas Petazzoni wrote:
> 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?
I have mainly been testing x86-64->x86 builds.
I tried doing a x86-64->qemu-arm-versatile build and it seems to boot
and run node.js properly (I am using 2012.08-rc2 with CodeSourcery ARM
2011.09 external toolchain).
Perhaps it needs a patch to build on an ARM host
(https://gist.github.com/1608607 might help).
Also, I was not able to get the qemu arm-versatile build to boot using
ext2 image and the qemu command in board/qemu/arm-versatile/readme.txt.
I get "Cannot open root device or unknown-block(0,0)" when it tries to
open /dev/sda.
Booting using a cpio initrd image works though.
Anything special I need to boot using ext2 image with ARM in qemu?
Regards,
Jonathan
prev parent reply other threads:[~2012-08-26 1:51 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
2012-08-25 17:17 ` Thomas Petazzoni
2012-08-26 1:51 ` Jonathan Liu [this message]
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=5039810B.7090200@gmail.com \
--to=net147@gmail.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