From: "Burton, Ross" <ross.burton@intel.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] libmnl: add recpie
Date: Wed, 30 Aug 2017 16:22:20 +0100 [thread overview]
Message-ID: <CAJTo0LaLmLLHErE4oE5_ivO87jZh71mX7BQbXTWdim1hyJV3fw@mail.gmail.com> (raw)
In-Reply-To: <CAHUNapQKyAK7F3TSf4Mi4xkGdjt99QL=j_+3nhYUUiuuA7UXRw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
On 30 August 2017 at 16:13, Trevor Woerner <twoerner@gmail.com> wrote:
> On Wed, Aug 30, 2017 at 6:53 AM, Burton, Ross <ross.burton@intel.com>
> wrote:
> > Note that we've reached feature freeze for 2.4 so this will have to wait
> for
> > 2.5.
>
> A lot of my builds failed last night because I'm not including
> meta-networking (which pulls in meta-python) because they weren't
> needed previously for what I was building. But with libmnl now being
> needed by iproute2, maybe this is a stronger argument for needing it
> in oecore for this release? oecore should stand on its own, unless
> there's a way to make this dependency a non-default packageconfig?
>
> It's not a big deal, I can just add meta-networking and meta-python
> and "solve" the problem.
How and why does oe-core need libmnl?
Ross
[-- Attachment #2: Type: text/html, Size: 1279 bytes --]
prev parent reply other threads:[~2017-08-30 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 7:25 [PATCH 1/2] libmnl: add recpie Yi Zhao
2017-08-29 7:25 ` [PATCH 2/2] iproute2: enable build tipc by default Yi Zhao
2017-08-29 16:13 ` Burton, Ross
2017-08-30 0:35 ` Yi Zhao
2017-08-30 7:43 ` Jussi Kukkonen
2017-08-31 0:53 ` Yi Zhao
2017-08-30 10:53 ` [PATCH 1/2] libmnl: add recpie Burton, Ross
2017-08-30 15:13 ` Trevor Woerner
2017-08-30 15:22 ` Burton, Ross [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=CAJTo0LaLmLLHErE4oE5_ivO87jZh71mX7BQbXTWdim1hyJV3fw@mail.gmail.com \
--to=ross.burton@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@gmail.com \
/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.