From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: meta-ti layer and tag 2012.05-yocto1.2
Date: Fri, 18 May 2012 05:56:16 -0600 [thread overview]
Message-ID: <4FB638E0.1010109@mlbassoc.com> (raw)
In-Reply-To: <CAFqH_52_fvqXtF5x_-6o84MZBA7LsGm4X87JVA4VftmWUihunw@mail.gmail.com>
On 2012-05-18 04:36, Enric Balletbò i Serra wrote:
> Hi Jack
>
> 2012/5/18 Jack Mitchell<ml@communistcode.co.uk>:
>> On 18/05/12 08:48, Enric Balletbò i Serra wrote:
>>>
>>> Hi all,
>>>
>>> Just to be sure, should the tag 2012.05-yocto1.2 from meta-ti layer be
>>> compatible with yocto-1.2 (denzil) branch ? Or also depends on other
>>> layers. Adding only the meta-ti layer to the yocto 1.2 seems is not
>>> working, there is an unmet dependency on systemd.bbclass.
>>>
>>> yocto-1.2$ bitbake core-image-minimal
>>> ERROR: ParseError at
>>>
>>> /home/eballetbo/Workspace/poky/yocto-1.2/meta-ti/recipes-misc/payload/bonescript.bb:5:
>>> Could not inherit file classes/systemd.bbclass
>>> ERROR: Command execution failed: Exited with 1
>>>
>>> Cheers,
>>> Enric
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>>
>> Hi Enric, to quote Denys from a patch to meta-ti earlier:
>>
>> README: by popular demand add comment on how to avoid systemd breakage
>>
>> Signed-off-by: Denys Dmytriyenko<denys@ti.com>
>>
>> ---
>>
>> README | 6 ++++++
>> 1 files changed, 6 insertions(+), 0 deletions(-)
>>
>> diff --git a/README b/README
>> index b376695..0df391f 100644
>> --- a/README
>> +++ b/README
>> @@ -11,6 +11,12 @@ layers: meta
>> branch: master
>>
>>
>> +When not depending on meta-openembedded and not using systemd, you may need
>> to
>> +mask few miscellaneous recipes requiring systemd, by adding this to
>> local.conf:
>> +
>> +BBMASK = "meta-ti/recipes-misc"
>> +
>> +
>> The base BSP part of meta-ti should work with different OpenEmbedded/Yocto
>> distributions and layer stacks, such as:
>> distro-less (only with OE-Core), with Yocto/Poky, with Angstrom or Arago.
>>
>
> Thanks, that works.
>
> I'm a bit confusing because the README of meta-ti layer says that this
> layer can only work with OE-core/Yocto but not sure that anyone has
> tested. For example bitbaking ti-dsplink recipe results on
>
> | make[1]: /arm-poky-linux-gnueabi-gcc: Command not found
>
> The problem seems that a lot of meta-ti recipes uses the
> TOOLCHAIN_PATH variable that is not defined in OE-core/Yocto or I'm
> wrong?. This don't look difficult to solve but are more surprises
> waiting for me after solve this ? Someone has tried this layer with
> only OE-core/Yocto ?
Yes, I have used it this way, however I'm using the master/tip, not the
mentioned tag.
I just built ti-dsplink using
meta = "master:38da655788361e949d605bebfab45cf5830df613"
meta-ti = "master:fa87ca0b1a1890d262a591aee50f082194f45317"
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2012-05-18 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 7:48 meta-ti layer and tag 2012.05-yocto1.2 Enric Balletbò i Serra
2012-05-18 9:01 ` Jack Mitchell
2012-05-18 10:36 ` Enric Balletbò i Serra
2012-05-18 11:56 ` Gary Thomas [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=4FB638E0.1010109@mlbassoc.com \
--to=gary@mlbassoc.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.