Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-openembedded] python_numpy: Fix SRC_URI warnings.
Date: Thu, 21 Jun 2012 21:28:50 -0700	[thread overview]
Message-ID: <4FE3F482.50506@gmail.com> (raw)
In-Reply-To: <1340338450-23907-1-git-send-email-elvis.dowson@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/21/2012 9:14 PM, Elvis Dowson wrote:
> 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  |   12
> +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
> 
> 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..bdcdf91 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 @@ -2,11
> +2,17 @@ DESCRIPTION = "A sophisticated Numeric Processing Package
> for Python" SECTION = "devel/python" LICENSE = "PSF" 
> LIC_FILES_CHKSUM =
> "file://LICENSE.txt;md5=3c42211d73c3faa1026e671dd39883fa" -PR =
> "r3" +PR = "r4"
> 
> SRC_URI = "${SOURCEFORGE_MIRROR}/numpy/numpy-${PV}.tar.gz \ -
> file://config.h \ -	   file://numpyconfig.h \ +	  " +SRC_URI_arm +=
> " \ +           file://arm/config.h \ +
> file://arm/numpyconfig.h \ +	  " +SRC_URI_mipsel += " \ +
> file://mipsel/config.h \ +           file://mipsel/numpyconfig.h \ 
> "
> 

Did you test it on arm/mipsel and made sure that SRC_URI is correct
after this change ?

> S = "${WORKDIR}/numpy-${PV}"
> 


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/j9IIACgkQuwUzVZGdMxRdNwCfRMpvWZtDIwMi4EkqZVhN9YbW
WPwAn3VFiygw3k119AqPDm7gxm8UVIl2
=NYbZ
-----END PGP SIGNATURE-----



  reply	other threads:[~2012-06-22  4:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22  4:14 [meta-openembedded] python_numpy: Fix SRC_URI warnings Elvis Dowson
2012-06-22  4:28 ` Khem Raj [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2012-06-22 14:28 Elvis Dowson
2012-06-28 17:10 ` 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=4FE3F482.50506@gmail.com \
    --to=raj.khem@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