From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: libc-common.bbclass and uclibc
Date: Thu, 26 Jul 2012 23:17:45 +0100 [thread overview]
Message-ID: <1343341065.4470.79.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAKSdS8LwF4XvBcuAoJ=36tOMMGF=VRLPoar5Tp9dCf+69JtiOw@mail.gmail.com>
On Thu, 2012-07-26 at 17:51 -0400, Manuel Bessler wrote:
> =========================================
> python populate_packages_prepend () {
> if d.getVar('DEBIAN_NAMES', True):
> bpn = d.getVar('BPN', True)
> d.setVar('PKG_'+bpn, 'libc6')
> ...
> =========================================
That particular piece of code does seem bogus for many reasons and
should probably go away. I think it is a historical relic.
But, that said, libc-common.bbclass is poorly named and is really
specific to (e)glibc. You don't want to use that for uclibc.
p.
next prev parent reply other threads:[~2012-07-26 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 21:51 libc-common.bbclass and uclibc Manuel Bessler
2012-07-26 22:07 ` Chris Larson
2012-07-26 22:17 ` Phil Blundell [this message]
2012-07-27 13:58 ` Manuel Bessler
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=1343341065.4470.79.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--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