From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Yocto + meta-networking
Date: Tue, 16 Jul 2013 22:28:57 +0100 [thread overview]
Message-ID: <59742333.4mCOApeMVS@helios> (raw)
In-Reply-To: <CAFZh4h-cZH_CU--Vsjq7=97HDbQXH67SCO5aKYR9cX7h4uNxuQ@mail.gmail.com>
Hi Brian,
On Tuesday 16 July 2013 17:06:46 Brian Hutchinson wrote:
> What is the "right" way of adding the meta-networking to Yocto? I'm
> obviously not doing something right.
>
> At the poky directory level, I cloned meta-openembedded. I then tried to
> go to my build's local.conf and adding meta-networking and meta-oe layers
> and I'm getting a dependency message when I try to bitbake net-snmp that
> says:
>
> ERROR: Layer dependency core of layer networking not found
>
> This makes me think that meta-openembedded is wanting openembedded-core but
> I've never tried to use that with Yocto before so I thought I better ask
> before I totally mess up my build environment.
>
> I have a rootfilesystem build based on Denzil and I need net-snmp and the
> meta-networking Denzil branch is pretty much empty so I cloned master in
> order to get net-snmp so I don't know if mixing branches could be my
> problem (don't know how much that matters but I usually try to use the same
> release branch of various components).
Mixing branches is the issue here. meta-networking added a LAYERDEPENDS on
"core" which the denzil poky/OE-Core doesn't provide. This is just an
incidental error though, if it hadn't failed on this you'd have hit other
problems.
meta-networking wasn't even around in the denzil days. If you need net-snmp
from there on top of denzil the only way is to backport the recipe and any
missing dependencies and add it to an additional layer (assuming you don't
already have a layer for customisations). In practice backporting should be
fairly trivial; I'd suggest copying the recipe over and seeing how far you
get.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-16 21:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 21:06 Yocto + meta-networking Brian Hutchinson
2013-07-16 21:19 ` Saul Wold
2013-07-16 21:47 ` Brian Hutchinson
2013-07-16 21:28 ` Paul Eggleton [this message]
2013-07-17 12:56 ` Brian Hutchinson
2013-07-17 13:03 ` Paul Eggleton
2013-07-17 13:12 ` Brian Hutchinson
2013-07-23 15:49 ` Denys Dmytriyenko
2013-07-23 14:36 ` Brian Hutchinson
2013-07-23 14:58 ` Paul Eggleton
2013-07-23 15:07 ` Brian Hutchinson
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=59742333.4mCOApeMVS@helios \
--to=paul.eggleton@linux.intel.com \
--cc=b.hutchman@gmail.com \
--cc=yocto@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.