From: Chong Lu <Chong.Lu@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] python-m2crypto: avoid swig problem
Date: Fri, 6 Jun 2014 18:08:35 +0800 [thread overview]
Message-ID: <53919323.80008@windriver.com> (raw)
In-Reply-To: <1402019165-23981-1-git-send-email-Chong.Lu@windriver.com>
On 06/06/2014 09:46 AM, Chong Lu wrote:
> Swig is used to generate C source and it has trouble processing opensslconf.h
> sometimes. So, we help it out when multilib variants exist.
>
> For native builds, the variant header will never exist.
>
> Specific multi-lib header files might be named *-32.h or *-n32.h, so we check
> for both names. We also might check for *-n64.h although that will never exist.
> It appears that *-o??.h will never exist, so we don't check for that.
>
> Signed-off-by: Joe Slater <jslater@windriver.com>
> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
> ---
> .../python/python-m2crypto_0.21.1.bb | 23 +++++++++++++++++++-
> 1 file changed, 22 insertions(+), 1 deletion(-)
>
> diff --git a/meta-oe/recipes-devtools/python/python-m2crypto_0.21.1.bb b/meta-oe/recipes-devtools/python/python-m2crypto_0.21.1.bb
> index 21c0269..4f0d785 100644
> --- a/meta-oe/recipes-devtools/python/python-m2crypto_0.21.1.bb
> +++ b/meta-oe/recipes-devtools/python/python-m2crypto_0.21.1.bb
> @@ -1,7 +1,7 @@
> SUMMARY = "A Python crypto and SSL toolkit"
> HOMEPAGE = "http://chandlerproject.org/bin/view/Projects/MeTooCrypto"
>
> -DEPENDS = "openssl swig-native"
> +DEPENDS = "openssl swig-native python"
>
> LICENSE = "BSD"
> LIC_FILES_CHKSUM = "file://LICENCE;md5=b0e1f0b7d0ce8a62c18b1287b991800e"
> @@ -20,4 +20,25 @@ SWIG_FEATURES_x86-64 = "-D__x86_64__"
> SWIG_FEATURES ?= ""
> export SWIG_FEATURES
>
> +# Get around a problem with swig, but only if the
> +# multilib header file exists.
> +#
> +do_compile_prepend() {
> + if [ "${baselib}" = "lib64" ];then
> + bit="64"
It's bad condition, ${baselib} != "lib64", maybe is a 64 bit.
I will resend V2.
BR
Chong
> + else
> + bit="32"
> + fi
> +
> + if [ -e ${STAGING_INCDIR}/openssl/opensslconf-${bit}.h ] ;then
> + for i in SWIG/_ec.i SWIG/_evp.i; do
> + sed -i -e "s/opensslconf.*\./opensslconf-${bit}\./" "$i"
> + done
> + elif [ -e ${STAGING_INCDIR}/openssl/opensslconf-n${bit}.h ] ;then
> + for i in SWIG/_ec.i SWIG/_evp.i; do
> + sed -i -e "s/opensslconf.*\./opensslconf-n${bit}\./" "$i"
> + done
> + fi
> +}
> +
> BBCLASSEXTEND = "native"
prev parent reply other threads:[~2014-06-06 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 1:46 [PATCH] python-m2crypto: avoid swig problem Chong Lu
2014-06-06 10:08 ` Chong Lu [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=53919323.80008@windriver.com \
--to=chong.lu@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.