From: Otavio Salvador <otavio@ossystems.com.br>
To: "ting.liu@freescale.com" <ting.liu@freescale.com>
Cc: meta-freescale <meta-freescale@yoctoproject.org>
Subject: Re: meta-fsl-ppc - layer.conf issues
Date: Wed, 6 Aug 2014 11:36:40 -0300 [thread overview]
Message-ID: <CAP9ODKrzwWUFLBfWbDU_gPAtjNjLcT1=Yw3bBHCyrE64hbVt6g@mail.gmail.com> (raw)
In-Reply-To: <d3f5a6fc82ec43c296e62a620fc2280d@BN1PR03MB156.namprd03.prod.outlook.com>
On Wed, Aug 6, 2014 at 11:21 AM, ting.liu@freescale.com
<ting.liu@freescale.com> wrote:
>> -----Original Message-----
>> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
>> bounces@yoctoproject.org] On Behalf Of Richard Purdie
>> Sent: Tuesday, August 05, 2014 6:09 PM
>> To: meta-freescale
>> Subject: [meta-freescale] meta-fsl-ppc - layer.conf issues
>>
>> Hi,
>>
>> I noticed that there is some "distro" policy creeping into meta-fsl-ppc's
>> layer.conf file, specifically:
>>
>> BB_DANGLINGAPPENDS_WARNONLY ?= "true"
>
> Hi Richard,
>
> this was added several days ago as a ppc specific patch for luajit (exist in mete-oe) was moved to
> ppc layer via bbappend. If not set, autobuilder for fsl-ppc will fail.
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/commit/?id=6367da32efce2736cd98f44fa358f0a9e578c08d
>
> do you have any recommendation to avoid this?
You can use the dynamic collections. Check how we deal with qt5 in meta-fsl-arm.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2014-08-06 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 10:09 meta-fsl-ppc - layer.conf issues Richard Purdie
2014-08-06 9:36 ` zhenhua.luo
2014-08-06 14:21 ` ting.liu
2014-08-06 14:36 ` Otavio Salvador [this message]
2014-08-07 2:47 ` ting.liu
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='CAP9ODKrzwWUFLBfWbDU_gPAtjNjLcT1=Yw3bBHCyrE64hbVt6g@mail.gmail.com' \
--to=otavio@ossystems.com.br \
--cc=meta-freescale@yoctoproject.org \
--cc=ting.liu@freescale.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.