From: Trevor Woerner <twoerner@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v2] nodejs: cleanup and update
Date: Mon, 21 Dec 2015 23:40:42 -0500 [thread overview]
Message-ID: <5678D44A.3040600@gmail.com> (raw)
In-Reply-To: <20151218115129.GE2563@jama>
On 12/18/15 06:51, Martin Jansa wrote:
> On Tue, Dec 01, 2015 at 01:19:25PM -0500, Trevor Woerner wrote:
>> Remove old nodejs_0.4.12 and update nodejs_0.12.7 to the latest stable
>> nodejs_4.2.2.
> It does something strange with CC and ends with invalid parameter for
> qemuarm:
>
> arm-oe-linux-gnueabi-g++: error: unrecognized argument in option '-mfpu=vfpv2'
>
> http://errors.yoctoproject.org/Errors/Details/22678/
Nodejs (actually V8) dropped support for ARMv5 around V8 version 3.22
https://github.com/nodejs/node/issues/3061
A day or so ago I had generated a patch to switch the -mfpu option to
"vfp" (i.e. version 1) instead of vfpv2 (-mfpu=vfp). This allowed nodejs
to build for ARMv5, but when I tried running it, it just crashed and
said "illegal instruction". Since ARMv5 is not supported upstream
anymore I didn't think it was worth my time trying to get it to work. So
I simply removed armv5 from COMPATIBLE_MACHINE. See my v3 patch.
As to this specific error, it doesn't look like gcc5 accepts "vfp2" as
an option to mfpu:
https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html
prev parent reply other threads:[~2015-12-22 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 18:19 [meta-oe][PATCH v2] nodejs: cleanup and update Trevor Woerner
2015-12-18 11:51 ` Martin Jansa
2015-12-22 4:40 ` Trevor Woerner [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=5678D44A.3040600@gmail.com \
--to=twoerner@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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