All of 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: Mon, 12 Jun 2017 16:39:54 +0000	[thread overview]
Message-ID: <bug-9941-163-PbU3MjqYHc@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9941-163@https.bugs.busybox.net/>

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

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |INVALID
                 CC|                            |yann.morin.1998 at free.fr

--- Comment #7 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Refik, All,

nodejs requires an FPU (VFP), but it is not enabled
in your Buildroot configuration.

So, if your CPU indeed lacks a VFP, then you can not
use nodejs on your target.

If your CPU does have a VFP, then enable it in your
Buildroot configuration.

Regards,
Yann E. MORIN.

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

      parent reply	other threads:[~2017-06-12 16:39 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 ` [Buildroot] [Bug 9941] " bugzilla at busybox.net
2017-06-07 12:33 ` 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 [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=bug-9941-163-PbU3MjqYHc@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 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.