From: "Eric Bénard" <eric@eukrea.com>
To: koen@dominion.thruhere.net
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][[RFC][PATCH] nodejs: add 0.8.18
Date: Wed, 30 Jan 2013 09:51:27 +0100 [thread overview]
Message-ID: <20130130095127.29acc1c8@e6520eb> (raw)
In-Reply-To: <1359532955-16954-1-git-send-email-koen@dominion.thruhere.net>
Hi Koen,
Le Wed, 30 Jan 2013 09:02:35 +0100,
Koen Kooi <koen@dominion.thruhere.net> a écrit :
> +++ b/meta-oe/recipes-devtools/nodejs/nodejs/0002-Enable-NEON.patch
> @@ -0,0 +1,27 @@
> +From 8891cb4cae57a6b7db54edb33a43743c4b09c53a Mon Sep 17 00:00:00 2001
> +From: Jason Kridner <jdk@ti.com>
> +Date: Wed, 7 Nov 2012 14:43:55 -0500
> +Subject: [PATCH] Enable NEON
> +
> +Read this was necessary on a blog.
> +
> +http://www.code-with-passion.com/2012/11/07/cross-compiling-nodejs-and-node-modules-for-armbeaglebone/
> +---
> + deps/v8/build/common.gypi | 1 +
> + 1 file changed, 1 insertion(+)
> +
> +diff --git a/deps/v8/build/common.gypi b/deps/v8/build/common.gypi
> +index 7a780cc..237f53f 100644
> +--- a/deps/v8/build/common.gypi
> ++++ b/deps/v8/build/common.gypi
> +@@ -29,6 +29,7 @@
> +
> + {
> + 'variables': {
> ++ 'arm_neon%': 1,
> + 'use_system_v8%': 0,
> + 'msvs_use_common_release': 0,
> + 'gcc_version%': 'unknown',
> +--
How will that behave on CPU without neon (armv5 for example) ?
Did you test it on qemu for example ?
Eric
next prev parent reply other threads:[~2013-01-30 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 8:02 [meta-oe][[RFC][PATCH] nodejs: add 0.8.18 Koen Kooi
2013-01-30 8:45 ` Koen Kooi
2013-01-30 8:51 ` Eric Bénard [this message]
2013-01-30 9:03 ` Koen Kooi
2013-01-30 9:06 ` Marcin Juszkiewicz
2013-01-31 16:56 ` Martin Jansa
2013-01-31 17:07 ` Koen Kooi
2013-01-31 18:00 ` Martin Jansa
2013-01-31 21:03 ` Koen Kooi
2013-02-08 8:50 ` Kevin Baker
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=20130130095127.29acc1c8@e6520eb \
--to=eric@eukrea.com \
--cc=koen@dominion.thruhere.net \
--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 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.