From: Elvis Dowson <elvis.dowson@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Elvis Dowson <elvis.dowson@gmail.com>
Subject: [meta-openembedded] python_numpy: Fix SRC_URI warnings.
Date: Fri, 22 Jun 2012 16:28:27 +0200 [thread overview]
Message-ID: <1340375307-20787-1-git-send-email-elvis.dowson@gmail.com> (raw)
This commit fixes the following warnings:
WARNING: Unable to get checksum for python-numpy SRC_URI entry config.h: file could not be found
WARNING: Unable to get checksum for python-numpy SRC_URI entry numpyconfig.h: file could not be found
Signed-off-by: Elvis Dowson <elvis.dowson@gmail.com>
---
.../recipes-devtools/python/python-numpy_1.4.1.bb | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/meta-oe/recipes-devtools/python/python-numpy_1.4.1.bb b/meta-oe/recipes-devtools/python/python-numpy_1.4.1.bb
index a67bf8b..0ae2ca2 100644
--- a/meta-oe/recipes-devtools/python/python-numpy_1.4.1.bb
+++ b/meta-oe/recipes-devtools/python/python-numpy_1.4.1.bb
@@ -5,7 +5,16 @@ LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=3c42211d73c3faa1026e671dd39883fa"
PR = "r3"
SRC_URI = "${SOURCEFORGE_MIRROR}/numpy/numpy-${PV}.tar.gz \
- file://config.h \
+ ${CONFIGFILESURI} \
+ "
+
+CONFIGFILESURI ?= ""
+
+CONFIGFILESURI_arm = "file://config.h \
+ file://numpyconfig.h \
+ "
+
+CONFIGFILESURI_mipsel = "file://config.h \
file://numpyconfig.h \
"
--
1.7.9.5
next reply other threads:[~2012-06-22 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 14:28 Elvis Dowson [this message]
2012-06-28 17:10 ` [meta-openembedded] python_numpy: Fix SRC_URI warnings Elvis Dowson
-- strict thread matches above, loose matches on Subject: below --
2012-06-22 4:14 Elvis Dowson
2012-06-22 4:28 ` Khem Raj
2012-06-22 4:39 ` Elvis Dowson
2012-06-22 4:45 ` Khem Raj
2012-06-22 5:16 ` Elvis Dowson
2012-06-22 5:18 ` Khem Raj
2012-06-22 4:51 ` Khem Raj
2012-06-22 14:15 ` Elvis Dowson
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=1340375307-20787-1-git-send-email-elvis.dowson@gmail.com \
--to=elvis.dowson@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