From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: Enable option of nodeJS 4.1.2 in buildroot 2015.11
Date: Sat, 12 Nov 2016 22:08:50 +0100 [thread overview]
Message-ID: <20161112210850.GB3700@free.fr> (raw)
In-Reply-To: <CALD51P_HZZzqLcn-JqLwdO95f8J8x3P6v4+L7fKZdtnGmo5t0g@mail.gmail.com>
Lijun, All,
On 2016-11-11 07:41 -0600, Lijun QIN spake thusly:
> Thank you so much for your help, Baruch
> I took your advice and applied the change to the Config.in in nodejs
> package. Since my .config does not have BR2_ARM_CPU_HAS_VFPV3, I used
> BR2_ARM_CPU_MAYBE_HAS_VFPV3 instead. The issue seems to have fixed.
This is definitely incorrect. The _MAYBE_HAS option is an internal one
that should not be used to derive the presence of abscence of VFPv3.
If your CPU does have VFPv3, then you must enable it with the correct
option, BR2_ARM_ENABLE_VFP "Enable VFP extension support", which has
been avaialble since f52692e: arch/arm: add option to enable an optional
VFP unit (and I should know, I did that patch in 2015! ;-) ).
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-11-12 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 1:28 [Buildroot] Enable option of nodeJS 4.1.2 in buildroot 2015.11 Lijun QIN
2016-11-11 4:37 ` Baruch Siach
2016-11-11 13:41 ` [Buildroot] Fwd: " Lijun QIN
2016-11-12 21:08 ` Yann E. MORIN [this message]
2016-11-11 14:00 ` [Buildroot] " Thomas Petazzoni
2016-11-12 21:01 ` Yann E. MORIN
2016-11-13 8:53 ` Thomas Petazzoni
2016-11-13 9:00 ` Yann E. MORIN
2016-11-13 11:11 ` Thomas Petazzoni
2016-11-14 2:10 ` Lijun QIN
2016-11-13 9:12 ` Baruch Siach
2016-11-12 21:13 ` Yann E. MORIN
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=20161112210850.GB3700@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox