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: Thu, 3 Mar 2016 16:01:35 +0100 [thread overview]
Message-ID: <20160303150135.GF2569@jama> (raw)
In-Reply-To: <CAJ86T=VFeZjULfZW3q06juYa90S8g93V7WhTB5Lgdhy+nJaprQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2043 bytes --]
On Mon, Feb 29, 2016 at 12:50:03PM -0800, Andre McCurdy 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.
Thanks!
After fixing the default in meta-qt5 I've started to see this issue in
other builds which were indeed built with
PREFERRED_VERSION_readline ?= "5.2"
to prevent GPLv3 readline being used by other components.
For gdb which isn't part of our release builds we can use bundled
readline, so I had to apply this no-static-libs.inc change and
explicitly remove readline from gdb's PACKAGECONFIG.
So to recap, meta-qt5 change fixed my jenkins "bitbake world" builds by
enabling system readline.
For internal builds (without GPLv3 where possible) on the other hand I
need to remove readline from PACKAGECONFIG and apply this fix to build
static readline inside gdb's build.
> (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 --]
next prev parent reply other threads:[~2016-03-03 14:59 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
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 [this message]
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=20160303150135.GF2569@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