From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Bring PREFERRED_LIBC to all distros
Date: Mon, 27 Apr 2009 13:32:43 -0400 [thread overview]
Message-ID: <49F5EC3B.1020505@balister.org> (raw)
In-Reply-To: <20090427165152.GN18788@smtp.west.cox.net>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
Tom Rini wrote:
> On Mon, Apr 27, 2009 at 06:45:02PM +0200, Koen Kooi wrote:
>> On 27-04-09 17:43, Tom Rini wrote:
>>> On Mon, Apr 27, 2009 at 05:33:31PM +0200, Koen Kooi wrote:
>>>> On 27-04-09 16:19, Tom Rini wrote:
>>>>> Hey all. I've created a new branch, trini/add-libc-overrides which does
>>>>> the following:
>>>>> - Make every distro declare PREFERRED_LIBC, either outright or
>>>>> overridable.
>>>> ACK on the idea, NACK on the implementation.
>>>>
>>>> ANGSTROMLIBC is called ANGSTROMLIBC and not ANGSTROM_LIBC for a reason,
>>>> since you can't pass env vars with underscores throught bitbake:
>>>> http://lists.linuxtogo.org/pipermail/openembedded-devel/2008-December/007258.html
>>> OK. But what about ANGSTROM_GCC_VERSION ? I've been passing that in
>>> via BB_ENV_EXTRAWHITE for a while and it's working, as far as I can
>>> tell.
>> With bitbake 1.8.12? If it's fixed in bitbake svn, great!
>
> Yeap. Even double-checked my build-dirs to be sure,
> tmp.4.1.2/work/armv6... has gcc-4.1.2 stuff in it.
What bitbake is in the stable branch? We should be careful forcing dev
to diverge stable for at least a few months ....
Of course, we can update .stables bitbake also.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-04-27 17:37 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 [this message]
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
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=49F5EC3B.1020505@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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.