From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Bring PREFERRED_LIBC to all distros
Date: Sun, 10 May 2009 23:03:36 +0200 [thread overview]
Message-ID: <gu7ff8$cmr$1@ger.gmane.org> (raw)
In-Reply-To: <20090510194704.GZ7973@smtp.west.cox.net>
On 10-05-09 21:47, Tom Rini wrote:
> On Sun, May 03, 2009 at 09:53:18AM -0700, Tom Rini wrote:
>> On Sun, May 03, 2009 at 02:29:53PM +0200, Leon Woestenberg wrote:
>>> Hello,
>>>
>>> On Sat, May 2, 2009 at 9:55 PM, Mike (mwester)<mwester@dls.net> wrote:
>>>> Acked-by: Mike Westerhof<mwester@dls.net>
>>>>
>>> I think we can add this functionality now.
>>>
>>> By the recent merge of "micro.conf" and "micro-uclibc.conf", a new
>>> TODO is to merge the LIBC feature into micro distro as well.
>>> See "[oe] Pull request from DoréDevelopment - New: Micro distro/image"
>>
>> I'll push this out Monday AM us. IMHO, for micro and micro-uclibc (and
>> similar for minimal/minimal-uclibc) is to merge them back into one and
>> make LIBC an easy override.
>
> So, here's a problem we've run into now. With distros that use
> debian.bbclass, having an OVERRIDE of 'glibc' added causes the glibc
> recipe to not create a 'glibc' package, nor a 'libc6' package. The
> libc6-dev package is created.
I suspect that's because ${PN} ('glibc') is now in overrides twice, try
changing the override to libc-glibc or something similar.
regards,
KOen
next prev parent reply other threads:[~2009-05-10 21:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 14:19 [RFC] Bring PREFERRED_LIBC to all distros Tom Rini
2009-04-27 14:22 ` [RFC][PATCH] All distro conf files: Use PREFERRED_LIBC to pick or set your libc Tom Rini
2009-04-27 14:23 ` [RFC][PATCH] Add distro inc files for eglibc, glibc and uclibc Tom Rini
2009-04-27 14:23 ` [RFC][PATCH] All distros: Bring in conf/distro/include/${PREFERRED_LIBC}.inc Tom Rini
2009-04-27 14:24 ` [RFC][PATCH] glibc: In various old recipes add RPROVIDES virtual-libc-dev, bump PR Tom Rini
2009-04-27 15:33 ` [RFC] Bring PREFERRED_LIBC to all distros Koen Kooi
2009-04-27 15:43 ` Tom Rini
2009-04-27 16:45 ` Koen Kooi
2009-04-27 16:51 ` Tom Rini
2009-04-27 17:32 ` Philip Balister
2009-04-27 17:36 ` Tom Rini
2009-04-27 15:35 ` Otavio Salvador
2009-04-29 16:06 ` Tom Rini
2009-04-28 20:30 ` Khem Raj
2009-04-28 20:55 ` Tom Rini
2009-04-29 5:40 ` Koen Kooi
2009-04-29 16:12 ` Tom Rini
2009-04-29 23:25 ` Leon Woestenberg
2009-05-02 19:55 ` Mike (mwester)
2009-05-03 12:29 ` Leon Woestenberg
2009-05-03 16:53 ` Tom Rini
2009-05-10 19:47 ` Tom Rini
2009-05-10 21:03 ` Koen Kooi [this message]
2009-05-10 21:51 ` Tom Rini
2009-05-10 22:27 ` Otavio Salvador
2009-05-10 22:36 ` Tom Rini
2009-05-11 7:03 ` Koen Kooi
2009-05-11 8:07 ` Richard Purdie
2009-05-11 8:27 ` Graeme Gregory
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='gu7ff8$cmr$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.