Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][meta-qt5] gdb: append to PACKAGECONFIG instead of changing the default
Date: Tue, 1 Mar 2016 09:44:34 +0100	[thread overview]
Message-ID: <20160301084434.GA6407@jama> (raw)
In-Reply-To: <1456793666-26638-1-git-send-email-Martin.Jansa@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

On Tue, Mar 01, 2016 at 01:54:26AM +0100, Martin Jansa wrote:
> * without readline in PACKAGECONFIG and with no-static-libraries.inc
>   gdb fails when trying to build against own bundled static readline
> 
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  recipes-devtools/gdb/gdb_%.bbappend | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-devtools/gdb/gdb_%.bbappend b/recipes-devtools/gdb/gdb_%.bbappend
> index 41592c4..ec17f55 100644
> --- a/recipes-devtools/gdb/gdb_%.bbappend
> +++ b/recipes-devtools/gdb/gdb_%.bbappend
> @@ -1 +1 @@
> -PACKAGECONFIG ??= "python"
> +PACKAGECONFIG_append = " python"

I should just change this to
PACKAGECONFIG ??= "readline python"

so that it is still easy for DISTROs to override this while fixing gdb
build with no-static-libraries.inc until
http://patchwork.openembedded.org/patch/116843/
is merged

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2016-03-01  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01  0:54 [PATCH][meta-qt5] gdb: append to PACKAGECONFIG instead of changing the default Martin Jansa
2016-03-01  8:44 ` Martin Jansa [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=20160301084434.GA6407@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox