From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [oe-commits] Ross Burton : glib-2.0: move more logic to the .inc
Date: Fri, 15 Nov 2013 22:37:05 +0100 [thread overview]
Message-ID: <20131115213705.GE31430@jama> (raw)
In-Reply-To: <20131112103426.B32915026B@opal>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Tue, Nov 12, 2013 at 10:34:26AM +0000, git@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: 55b950500fd9d944042e3c2b0872685f0a60e8eb
> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=55b950500fd9d944042e3c2b0872685f0a60e8eb
>
> Author: Ross Burton <ross.burton@intel.com>
> Date: Fri Nov 8 16:06:38 2013 +0000
>
> glib-2.0: move more logic to the .inc
>
> The .bb was getting larger with configuration being arbitarily split between .bb
> and .inc. To help adding a glib_git recipe, strip the .bb down to SRC_URI.
>
> Also don't remove $libdir/gio as it should be owned by glib.
IIRC we had fix for this QA warning before and now I see it again:
WARNING: QA Issue: glib-2.0-dbg: found library in wrong location:
/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.1-gdb.py
glib-2.0-dbg: found library in wrong location:
/usr/share/gdb/auto-load/usr/lib64/libglib-2.0.so.0.3800.1-gdb.py
Is it possible that something was left out? I don't know since when I
have this warning, so it could be since last glib-2.0 upgrade as well.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next parent reply other threads:[~2013-11-15 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131112103426.B32915026B@opal>
2013-11-15 21:37 ` Martin Jansa [this message]
2013-11-15 22:08 ` [oe-commits] Ross Burton : glib-2.0: move more logic to the .inc Khem Raj
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=20131115213705.GE31430@jama \
--to=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.