All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Gagneraud <chgans@gna.org>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [arago/yocto-1.3] crda and python-m2crypto
Date: Wed, 17 Jul 2013 09:28:16 +1200	[thread overview]
Message-ID: <51E5BAF0.10206@gna.org> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED101596576BD@DLEE11.ent.ti.com>

On 17/07/13 00:58, Maupin, Chase wrote:
>> -----Original Message-----
>> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
>> bounces@arago-project.org] On Behalf Of Christian Gagneraud
>> Sent: Monday, July 15, 2013 12:21 AM
>> To: meta-arago@arago-project.org
>> Subject: [meta-arago] [arago/yocto-1.3] crda and python-m2crypto
>>
>> Hi,
>>
>> While building an image with arago-stable/yocto-1.3, I encountered
>> an error:
>> DEBUG: Executing shell function do_compile
>> NOTE: make -j 8 MAKEFLAGS= all_noverify
>>    GEN  keys-gcrypt.c
>>    CC   crda.o
>>    CC   intersect.o
>>    Trusted pubkeys: pubkeys/linville.key.pub.pem
>>    CC   print-regdom.o
>>    CC   regdbdump.o
>> ERROR: Failed to import the "M2Crypto" module: No module named
>> M2Crypto
>> Please install the "M2Crypto" Python module.
>> On Debian GNU/Linux the package is called "python-m2crypto".
>> make: *** [keys-gcrypt.c] Error 1
>> make: *** Waiting for unfinished jobs....
>> ERROR: oe_runmake failed
>> ERROR: Function failed: do_compile (see
>> /home/christiaga/projects/yocto/arago/build/arago-tmp-external-
>> linaro-toolchain/work\
>> /armv7ahf-vfp-neon-oe-linux-gnueabi/crda-1.1.1-
>> r0/temp/log.do_compile.15753
>> for further information)
>>
>> Basically crda doesn't build because it needs python-m2crypto,
>> i've
>> installed it via apt-get and everything was fine then.
>> This is not documented in [1], [2] nor in [3].
>>
>> After digging a bit I found that the CRDA recipe comes from
>> arago-distro-extras, but it can be found in
>> meta-openembedded/meta-networking (on master, not on danny branch)
>> as
>> well. Looking at [4], it seems this version would have this
>> dependency
>> built by bitbake (python-m2crypto-native), again python-m2crypto-
>> native
>> is available only on master, not on danny.
>
> In the meta-arago danny branch there is a python-m2crypto recipe
> that extends native. So can you add the DEPENDS on
> python-m2crypto-native to the crda recipe with danny and have this
> work? Is that the solution you  are mentioning?

You are right, and actually crda (from meta-arago) already depends on 
python-m2crypto-native.
Anyway, it doesn't seem to be enough as my build failed, and I had to 
install my distro version of python-m2crypto to fix this (unless it got 
fixed as a side effect of re-running bitbake).

I might clean and rebuild everything, I thought I could update the 
layers without rebuilding everything from scratch, in theory it should 
work, but in practice I'm not sure it does, as I had a couple of issues 
(after my last update) that doesn't make sense to others (BlueZ version 
issue, Qt  and now crda).

Thanks,
Chris

>>
>> Do you want me to open a bug report somewhere?
>>
>> Regards,
>> Chris
>>
>> [1]
>> http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-
>> project-qs.html
>> [2]
>> http://arago-
>> project.org/wiki/index.php/Setting_Up_Build_Environment#Host_tools
>> [3] http://www.openembedded.org/wiki/Getting_started
>> [4]
>> _______________________________________________
>> meta-arago mailing list
>> meta-arago@arago-project.org
>> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago



  reply	other threads:[~2013-07-16 21:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15  5:21 [arago/yocto-1.3] crda and python-m2crypto Christian Gagneraud
2013-07-16 12:58 ` Maupin, Chase
2013-07-16 21:28   ` Christian Gagneraud [this message]
2013-07-16 21:32     ` Maupin, Chase
2013-07-17 21:28     ` Dmytriyenko, Denys

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=51E5BAF0.10206@gna.org \
    --to=chgans@gna.org \
    --cc=chase.maupin@ti.com \
    --cc=meta-arago@arago-project.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.