All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Kang Kai <Kai.Kang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] eglibc-dbg: provides libc6-dbg
Date: Sat, 25 Jan 2014 19:30:45 +0000	[thread overview]
Message-ID: <1390678245.24755.51.camel@e130.pbcl.net> (raw)
In-Reply-To: <52DF8A1E.9050306@windriver.com>

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.

p.




  reply	other threads:[~2014-01-25 19:30 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 [this message]
2014-01-27  3:20       ` Kang Kai
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=1390678245.24755.51.camel@e130.pbcl.net \
    --to=pb@pbcl.net \
    --cc=Kai.Kang@windriver.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.