All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: liu.ming50@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] meta: conf: avoid appending LIBCOVERRIDE to OVERRIDES
Date: Sat, 07 Apr 2018 11:25:44 +0100	[thread overview]
Message-ID: <1523096744.2942.54.camel@linuxfoundation.org> (raw)
In-Reply-To: <1523091927-15811-1-git-send-email-liu.ming50@gmail.com>

On Sat, 2018-04-07 at 11:05 +0200, liu.ming50@gmail.com wrote:
> From: Ming Liu <liu.ming50@gmail.com>
> 
> The order of any other overrides should be before forcevariable, or
> else it will get the highest priority.
> 
> Signed-off-by: Ming Liu <liu.ming50@gmail.com>
> ---
>  meta/classes/native.bbclass                   | 2 --
>  meta/classes/nativesdk.bbclass                | 2 +-
>  meta/conf/bitbake.conf                        | 3 ++-
>  meta/conf/distro/include/tclibc-baremetal.inc | 5 ++---
>  meta/conf/distro/include/tclibc-glibc.inc     | 5 ++---
>  meta/conf/distro/include/tclibc-musl.inc      | 5 ++---
>  6 files changed, 9 insertions(+), 13 deletions(-)

We do not want to inject an empty entry into OVERRIDES. This patch
changes things so we can end up with "::" in there.

I suspect we've fixed bugs in bitbake where problems resulted from that
however I still don't want to do it.

Cheers,

Richard


      reply	other threads:[~2018-04-07 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07  9:05 [PATCH] meta: conf: avoid appending LIBCOVERRIDE to OVERRIDES liu.ming50
2018-04-07 10:25 ` Richard Purdie [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=1523096744.2942.54.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liu.ming50@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.