From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Khem Raj <raj.khem@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: should layers define BB_DANGLINGAPPENDS_WARNONLY ?= "1"?
Date: Tue, 3 Nov 2015 06:15:33 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1511030615020.12109@localhost> (raw)
In-Reply-To: <CAMKF1spGWN8dDzQ5wcE7f_U2JJuk=7VE_onpDORN-SMNqHgf-g@mail.gmail.com>
On Mon, 2 Nov 2015, Khem Raj wrote:
> On Mon, Nov 2, 2015 at 9:54 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> > perusing the meta-musl layer, and noticed in layer.conf the line:
> >
> > BB_DANGLINGAPPENDS_WARNONLY ?= "1"
>
> should be avoided although meta-musl is a bit core in nature.
> this is so that it can interface with several different compilers
> coming from different layers and also different oe-core releases can
> work with same branch of meta-musl.
> one may not have same layers attached to it. Ideally, those patches
> should now become part
> of the original layers as they have been accepted in gcc upstream and
> so on. Hopefully as I will take
> this into oe-core in coming months this should disappear.
ok, that's fair ... i didn't consider this a major issue, i just
thought it was a bit odd.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2015-11-03 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 17:54 should layers define BB_DANGLINGAPPENDS_WARNONLY ?= "1"? Robert P. J. Day
2015-11-02 18:01 ` Paul Eggleton
2015-11-02 18:03 ` Gary Thomas
2015-11-02 21:37 ` Khem Raj
2015-11-03 11:15 ` Robert P. J. Day [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=alpine.LFD.2.20.1511030615020.12109@localhost \
--to=rpjday@crashcourse.ca \
--cc=raj.khem@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.