All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ross Burton" <ross@burtonini.com>
To: Tim Orling <ticotimo@gmail.com>
Cc: Peter Smith <salerio@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] [meta-zephyr] bitbake zephyr-helloworld configure failure
Date: Tue, 2 Feb 2021 10:29:48 +0000	[thread overview]
Message-ID: <CAAnfSTuyR1bE0jaPdNSp6g0u7dRfKtRHr2gnd0ZgLNyQjdu8zQ@mail.gmail.com> (raw)
In-Reply-To: <CANx9H-DvpKkPpQnMMnFBSnVEvFXiWMHOmxT1iaCUeigp51yTmA@mail.gmail.com>

I sent a patch to meta-oe yesterday: there was a missing dependency in
python3-kwalify and missing class extend in the ruamel recipe.

Ross

On Thu, 28 Jan 2021 at 05:49, Tim Orling <ticotimo@gmail.com> wrote:
>
>
>
> On Wed, Jan 27, 2021 at 12:51 AM Peter Smith <salerio@gmail.com> wrote:
>>
>> Using master branch
>>
>> MACHINE=96b_nitrogen bitbake zephyr-helloworld creates a configure error due to a failure for native python to import ruamel.
>>
>> I fixed this temporarily by creating a python3-ruamel-yaml_%.bbappend that includes the required BBEXTEND and adding python3-ruamel-yaml-native to zephyr-kernel-common.inc.
>>
>> I don't know (not enough experience) if this is actually a problem in the meta-openembedded recipe or meta-zephyr?
>
>
>
> BBEXTEND = “native” is a perfectly fine patch to submit to meta-python. We tend to only make those changes when needed (as in your use case) rather than universally. Please submit a patch :)
>>
>>
>> Best Regards
>> Peter
>>
>>
>>
>
> 
>

  reply	other threads:[~2021-02-02 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27  8:56 [meta-zephyr] bitbake zephyr-helloworld configure failure Peter Smith
2021-01-28  5:48 ` [yocto] " Tim Orling
2021-02-02 10:29   ` Ross Burton [this message]
2021-02-02 18:20     ` Khem Raj
2021-02-03 16:57       ` Peter Smith

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=CAAnfSTuyR1bE0jaPdNSp6g0u7dRfKtRHr2gnd0ZgLNyQjdu8zQ@mail.gmail.com \
    --to=ross@burtonini.com \
    --cc=salerio@gmail.com \
    --cc=ticotimo@gmail.com \
    --cc=yocto@lists.yoctoproject.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.