All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
	Andre McCurdy <armccurdy@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] no-static-libs.inc: add gdb
Date: Tue, 01 Mar 2016 08:04:27 +0000	[thread overview]
Message-ID: <1456819467.11498.185.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160301004309.GA2559@jama>

On Tue, 2016-03-01 at 01:43 +0100, Martin Jansa wrote:
> On Mon, Feb 29, 2016 at 10:30:17PM +0100, Martin Jansa wrote:
> > No special configuration IIRC (will check tomorrow and send whole
> > config.log).
> > 
> > But it failed the same in my minimal chroot env with just oe-core
> > and on
> > Ubuntu jenkins slave doing bitbake world with many layers, here is
> > full log:
> > http://errors.yoctoproject.org/Errors/Details/38149/
> > 
> > and it shows --without-system-readline parameter.
> 
> It's caused by bbappend in meta-qt5
> 
> OE qemux86@ ~/build/oe-core $ cat meta-qt5/recipes
> -devtools/gdb/gdb_%.bbappend
> PACKAGECONFIG ??= "python"
> 
> But on the other hand does this change make more harm than confusing
> error for people who try to build without readline in PACKAGECONFIG?

I mainly wanted to understand what configuration caused this, which we
now understand/ I agree we should probably do something about the
error.

I do wonder what a gdb bbappend is doing in meta-qt5 though. I'd say
that is really "distro" configuration.

Cheers,

Richard




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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 19:10 [PATCH] no-static-libs.inc: add gdb Martin Jansa
2016-02-29 20:40 ` Richard Purdie
2016-02-29 20:43   ` Burton, Ross
2016-02-29 20:50     ` Andre McCurdy
2016-02-29 21:30       ` Martin Jansa
2016-03-01  0:43         ` Martin Jansa
2016-03-01  8:04           ` Richard Purdie [this message]
2016-03-01  8:11             ` Martin Jansa
2016-03-01  8:40           ` Burton, Ross
2016-03-01  8:59             ` Martin Jansa
2016-03-03 15:01       ` Martin Jansa
2016-03-03 17:19       ` Burton, Ross
2016-03-03 20:51         ` Burton, Ross

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=1456819467.11498.185.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.com \
    --cc=martin.jansa@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.