All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [v4 1/4] package/nodejs: Add node.js v0.12.5 and set as the default version
Date: Mon, 12 Oct 2015 18:51:51 +0200	[thread overview]
Message-ID: <20151012165150.GD3735@free.fr> (raw)
In-Reply-To: <CAFGQKxd9DJUmqHrCUHRD+VMvYfG5fC-87xJZhb3PG-1HFpOHeQ@mail.gmail.com>

MArtin, All,

On 2015-10-12 09:48 +0100, Martin Bark spake thusly:
> On 11 October 2015 at 20:25, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Martin, All,
> >
> > On 2015-07-02 10:43 +0100, Martin Bark spake thusly:
> >> The version of the V8 JavaScript engine used by node.js v0.12.5 requires
> >> at least an ARMv6 architecture with VFPv2.
> >
> > I'm trying to bump to node.js 4.1.2 and was wondering if that limitation
> > still exists in that version.
> 
> Yes I've been thinking about this too.  As far as i can tell v0.10.x
> was the last release to support ARMv5 due to changes in the V8
> JavaScript engine.  One thing i have been wondering is if we need to
> support multiple versions of node.js or just 4.1.x?  The node.js LTS
> working group here https://github.com/nodejs/LTS/ seems to say that
> 0.10.x and 0.12.x are still being maintained but supporting only the
> latest version would be simpler.  What do you think?

We currently have kept nodejs 0.10.x for backward compatibility with
armv5 or non-VFP CPUs, in parallel with 0.12.x for armv6+ with VFP CPUs.

> > I was able to sucessfully build for an arm926t (armv5) with a VFPv2 FPU.
> >
> > So:
> >   - is the failure a runtime failure or a build time one?
> 
> From memory it only show up at runtime as an illegal instruction.  I
> think i tested using qemu_arm_versatile_defconfig and a simple test
> like
> 
>     node -e 'console.log("hello world");'
> 
> >   - is armv6 really required, or can we just require VFPv2?
> 
> I went off this announcement for V8
> https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk where it
> states the minimum is now ARMv6 with VFPv2.  It was the no-VFPv2 port
> that was removed but i don't know if it also requires any ARMv6 or
> higher instructions.  The node.js configure script only seems to check
> form ARMv6 or ARMv7, see
> https://github.com/nodejs/node/blob/master/configure#L616.  So i
> assume node.js and V8 need a minimum ARMv6 instruction set.

OK, so let's do as upstream wants it:

  - armv6 or above ir required
  - VFPv2 or above is required

Thanks! :-)

BTW, you can see my WIP patch there (moving target, the branch may get
rebased from time to time; handle with care! ;-) ):
    http://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/node

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2015-10-12 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  9:43 [Buildroot] [v4 1/4] package/nodejs: Add node.js v0.12.5 and set as the default version Martin Bark
2015-07-02  9:43 ` [Buildroot] [v4 2/4] package/nodejs: symlink /usr/lib/node_modules/.bin/* to /usr/bin Martin Bark
2015-07-02  9:43 ` [Buildroot] [v4 3/4] package/nodejs: Fixes for node-pre-gyp Martin Bark
2015-07-02 21:54   ` Yann E. MORIN
2015-07-04  6:51     ` Jörg Krause
2015-07-02  9:43 ` [Buildroot] [v4 4/4] package/nodejs: Define NPM command for other packages to use Martin Bark
2015-07-02 21:51 ` [Buildroot] [v4 1/4] package/nodejs: Add node.js v0.12.5 and set as the default version Yann E. MORIN
2015-07-04 12:56 ` Thomas Petazzoni
2015-07-05 19:07   ` Martin Bark
2015-10-11 19:25 ` Yann E. MORIN
2015-10-12  8:48   ` Martin Bark
2015-10-12 16:51     ` Yann E. MORIN [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=20151012165150.GD3735@free.fr \
    --to=yann.morin.1998@free.fr \
    --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.