From: Amy Fong <amy.fong@windriver.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe] [PATCH] [v2] nodejs needs python-native (Was: Re: [meta-oe] [PATCH] nodejs needs python-native)
Date: Tue, 27 May 2014 12:54:29 -0400 [thread overview]
Message-ID: <20140527165429.GA26798@windriver.com> (raw)
In-Reply-To: <20140520190315.GA32657@windriver.com>
From 1f1029bff98bd52a52a5bf81f4f36ca86d28f8cd Mon Sep 17 00:00:00 2001
From: Amy Fong <amy.fong@windriver.com>
Date: Tue, 27 May 2014 12:52:00 -0400
Subject: [PATCH] nodejs needs python-native
nodejs should use python from python-native package. On some hosts, the
default python is missing bz2 support.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
---
meta-oe/recipes-devtools/nodejs/nodejs_0.8.18.bb | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs_0.8.18.bb b/meta-oe/recipes-devtools/nodejs/nodejs_0.8.18.bb
index 996d68e..28cf0d6 100644
--- a/meta-oe/recipes-devtools/nodejs/nodejs_0.8.18.bb
+++ b/meta-oe/recipes-devtools/nodejs/nodejs_0.8.18.bb
@@ -5,6 +5,8 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=95a589a3257ab7dfe37d8a8379e3c72d"
DEPENDS = "openssl"
+inherit pythonnative
+
SRC_URI = "http://nodejs.org/dist/v${PV}/node-v${PV}.tar.gz \
file://0001-gcc-has-a-builtin-define-to-denote-hard-abi-when-in-.patch \
"
@@ -40,3 +42,6 @@ RDEPENDS_${PN}_class-native = ""
FILES_${PN} += "${libdir}/node/wafadmin ${libdir}/node_modules ${libdir}/dtrace"
BBCLASSEXTEND = "native"
+
+FILES_${PN} += "${libdir}/*"
+
--
2.0.0.rc0
prev parent reply other threads:[~2014-05-27 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 19:03 [meta-oe] [PATCH] nodejs needs python-native Amy Fong
2014-05-20 19:28 ` Khem Raj
2014-05-20 19:56 ` Gary Thomas
2014-05-27 16:54 ` Amy Fong [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=20140527165429.GA26798@windriver.com \
--to=amy.fong@windriver.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 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.