Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] guile, mailx, gcc, opensp, gstreamer1.0-libav, libunwind: disable thumb where it fails for qemuarm
Date: Thu, 14 May 2015 13:40:02 +0200	[thread overview]
Message-ID: <20150514114002.GA2402@jama> (raw)
In-Reply-To: <1431600497.30971.208.camel@linuxfoundation.org>

On Thu, May 14, 2015 at 11:48:17AM +0100, Richard Purdie wrote:
> On Wed, 2015-05-13 at 14:30 +0200, Martin Jansa wrote:
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> >  meta/recipes-devtools/gcc/gcc_4.9.bb               | 23 ++++++++++++++++++++++
> >  meta/recipes-devtools/guile/guile_2.0.11.bb        | 19 ++++++++++++++++++
> >  meta/recipes-devtools/opensp/opensp_1.5.2.bb       |  5 +++++
> >  meta/recipes-extended/mailx/mailx_12.5.bb          |  4 ++++
> >  .../gstreamer/gstreamer1.0-libav_1.4.5.bb          |  9 +++++++++
> >  meta/recipes-support/libunwind/libunwind_1.1.bb    |  6 ++++++
> >  6 files changed, 66 insertions(+)
> 
> As mentioned on the bug relating to this, I think we should create an
> include file which sets the values as needed for these recipes rather
> than adding the quite long comments to the recipes themselves. This is
> similar to what we do where we know there are security flags issues for
> example.

Is it OK, to put overrides for recipes in other layers to .inc file in
oe-core? If yes then I agree and will convert this into .inc file in
conf/machine/include/ (included by default for thumb1 machine tunes)


-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com


  reply	other threads:[~2015-05-14 11:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 12:30 [PATCH] guile, mailx, gcc, opensp, gstreamer1.0-libav, libunwind: disable thumb where it fails for qemuarm Martin Jansa
2015-05-14 10:48 ` Richard Purdie
2015-05-14 11:40   ` Martin Jansa [this message]
2015-10-09 15:11     ` [PATCH] webkitgtk, gcr, libsecret: force ARM mode Martin Jansa
2015-10-10 12:13       ` Carlos Alberto Lopez Perez
2015-10-10 15:32         ` Martin Jansa
2015-10-10 21:45           ` Carlos Alberto Lopez Perez
2015-10-10 21:59             ` Khem Raj
2015-10-12  8:03             ` Martin Jansa
2015-10-12 11:17             ` Alexander Kanavin
2015-10-12 22:26               ` Carlos Alberto Lopez Perez
2015-10-10 19:15         ` Khem Raj
2015-10-11  9:51       ` Phil Blundell
2015-10-12 16:21         ` Burton, Ross
2015-10-14 11:22 ` [PATCH] guile, mailx, gcc, opensp, gstreamer1.0-libav, libunwind: disable thumb where it fails for qemuarm Martin Jansa

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=20150514114002.GA2402@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox