Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9941] nodejs option disappears for arm
Date: Wed, 07 Jun 2017 12:28:37 +0000	[thread overview]
Message-ID: <bug-9941-163-Nei9UumY1m@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9941-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9941

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Peter Korsgaard <jacmet@uclibc.org> ---
With ARM I take it that you specifically mean one of the older ARM variants
(arm926t or similar)? Modern versions of nodejs require instructions only
available on ARMv6 + FPU or newer. In 2016.11 we still supported the legacy
0.10.x version of nodejs for the older ARM variants, but this is no longer
supported by nodejs upstream and got removed from Buildroot back in March.

If your system really has such an old ARM variant then you cannot use nodejs,
unless you re-add the (unsupported) 0.10.x version or stick with with our
current LTS release (2017.02.x)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2017-06-07 12:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07  8:58 [Buildroot] [Bug 9941] New: nodejs option disappears for arm bugzilla at busybox.net
2017-06-07 12:28 ` bugzilla at busybox.net [this message]
2017-06-07 12:33 ` [Buildroot] [Bug 9941] " bugzilla at busybox.net
2017-06-07 13:03 ` bugzilla at busybox.net
2017-06-07 14:18 ` bugzilla at busybox.net
2017-06-07 14:51 ` bugzilla at busybox.net
2017-06-12 12:59 ` bugzilla at busybox.net
2017-06-12 16:39 ` bugzilla at busybox.net

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=bug-9941-163-Nei9UumY1m@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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