Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] no-static-libs.inc: add gdb
Date: Tue, 1 Mar 2016 01:43:09 +0100	[thread overview]
Message-ID: <20160301004309.GA2559@jama> (raw)
In-Reply-To: <CA+chaQfHZPKviheG2NY7miXe9YZir0pszp8qCQbb1kgzPABPDQ@mail.gmail.com>

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

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?

Regards,

> 
> On Mon, Feb 29, 2016 at 9:50 PM, Andre McCurdy <armccurdy@gmail.com> wrote:
> 
> > On Mon, Feb 29, 2016 at 12:43 PM, Burton, Ross <ross.burton@intel.com>
> > wrote:
> > >
> > > On 29 February 2016 at 20:40, Richard Purdie
> > > <richard.purdie@linuxfoundation.org> wrote:
> > >>
> > >> I'm a bit puzzled as our autobuilders build this all the time and we
> > >> don't see failures. Any idea what the configuration difference might
> > >> be?
> > >
> > > Since oe-core 94e1b917078bedf73830e54278af77f742c93581 gdb has a
> > > packageconfig for system readline, which is enabled by default (and has
> > been
> > > enabled explicitly for a long time).  Do you have some local patches
> > adding
> > > more PACKAGECONFIG options but not enabling readline?
> >
> > gdb 7.10.1 depends on readline features which are not present in
> > readline 5.2 (ie the GPLv2 version). Using the gdb internal readline
> > is a workaround for people who don't want to switch to the GPLv3
> > version of readline.
> >
> > (Although gdb is itself GPLv3, it's self contained and easy to exclude
> > from release builds).
> >
> > > Ross
> > >
> > > --
> > > _______________________________________________
> > > Openembedded-core mailing list
> > > Openembedded-core@lists.openembedded.org
> > > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> > >
> >

-- 
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  0:41 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 [this message]
2016-03-01  8:04           ` Richard Purdie
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=20160301004309.GA2559@jama \
    --to=martin.jansa@gmail.com \
    --cc=armccurdy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox