From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Support building all project in one directory
Date: Fri, 15 Jan 2010 12:00:31 +0100 [thread overview]
Message-ID: <hiphse$ulj$1@ger.gmane.org> (raw)
In-Reply-To: <op.u6klcvzcmn1qzu@guohr-laptop-ubuntu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 15-01-10 11:42, Guo Hongruan wrote:
> 在 Fri, 15 Jan 2010 17:56:39 +0800，Phil Blundell <philb@gnu.org> 写道:
>
>> For the majority of DISTROs, there is only a single supported C library
>> anyway so there should be no ambiguity. For example, if you build for
>> micro-uclibc, that means you are using uClibc. If you build for micro,
>> that means you are using eglibc.
>
> OE should provide a mechanism which should not restrict one certain libc
> type.
>
> Even though every distro supports only one libc type
Angstrom supports glibc, uclibc and eglibc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLUErPMkyGM64RGpERAt7EAKCx70to28K9IdhgjCmqyyL0N2ZIIQCfSJt8
ZcsK/7uJIjVbkKQWZTYjJCA=
=q9F7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-15 11:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 7:55 [PATCH] Support building all project in one directory Guo Hongruan
2010-01-14 9:14 ` Marcin Juszkiewicz
2010-01-14 9:19 ` Guo Hongruan
2010-01-14 19:53 ` Khem Raj
2010-01-15 1:35 ` Guo Hongruan
2010-01-15 3:47 ` Mike Westerhof
2010-01-15 9:17 ` Guo Hongruan
2010-01-15 9:56 ` Phil Blundell
2010-01-15 10:42 ` Guo Hongruan
2010-01-15 10:46 ` Phil Blundell
2010-01-15 10:59 ` Guo Hongruan
2010-01-15 12:50 ` Phil Blundell
2010-01-15 12:57 ` Guo Hongruan
2010-01-15 13:02 ` Phil Blundell
2010-01-15 13:09 ` Guo Hongruan
2010-01-15 11:00 ` Koen Kooi [this message]
2010-01-15 10:43 ` Guo Hongruan
2010-01-15 6:33 ` Marcin Juszkiewicz
2010-01-15 8:23 ` Koen Kooi
2010-01-15 9:23 ` Guo Hongruan
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='hiphse$ulj$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.