From: Kang Kai <Kai.Kang@windriver.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] eglibc-dbg: provides libc6-dbg
Date: Mon, 27 Jan 2014 11:20:09 +0800 [thread overview]
Message-ID: <52E5D069.5040209@windriver.com> (raw)
In-Reply-To: <1390678245.24755.51.camel@e130.pbcl.net>
On 2014年01月26日 03:30, Phil Blundell wrote:
> On Wed, 2014-01-22 at 17:06 +0800, Kang Kai wrote:
>> Use glib-dbg does work. But if I use it in a recipe, when uclibc is
>> used, I have to edit the recipe.
> Isn't that still true of "libc6-dbg"? Worse, it isn't even guaranteed
> that the eglibc-debug package will be named libc6-dbg on all targets; it
> would probably end up as libc6.1-dbg on alpha-linux or ia64-linux for
> example. Encouraging people to hardcode "libc6" doesn't seem very
> wholesome.
I think this is the way to deal the "RPROVIDES" and please ref to
libc6-dev in eglibc-package.inc:
RPROVIDES_${PN}-dev = "glibc-dev libc6-dev virtual-libc-dev"
Thanks,
Kai
>
> p.
>
>
>
--
Regards,
Neil | Kai Kang
next prev parent reply other threads:[~2014-01-27 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 3:12 [PATCH] eglibc-dbg: provides libc6-dbg Kai Kang
2014-01-22 7:08 ` Phil Blundell
2014-01-22 9:06 ` Kang Kai
2014-01-25 19:30 ` Phil Blundell
2014-01-27 3:20 ` Kang Kai [this message]
2014-01-27 11:25 ` Phil Blundell
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=52E5D069.5040209@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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.