From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
Cc: oe-core layer <openembedded-core@lists.openembedded.org>, Patches
Subject: Re: uclibc sdk issue
Date: Mon, 29 Oct 2012 10:14:08 +0000 [thread overview]
Message-ID: <1351505648.2828.2.camel@ted> (raw)
In-Reply-To: <CAOHjBZswZPW6f_4ugCJcJ9w4=y9bt6ADvVd0gjtEnFuiXB-1kw@mail.gmail.com>
On Mon, 2012-10-29 at 09:48 +0100, Giuseppe Condorelli wrote:
> Hi Khem,
>
> what I want to build is the meta-toolchain (uclibc) and looking at the
> build I can see system tries to build also eglibc packages.
> Maybe I'm wrong in something.
> Welcome advice.
So that the toolchain can be used on many different systems the
toolchain binaries themselves link against their own libc which ships as
part of meta-toolchain. We use eglibc for this and uclibc is not
supported.
The target libc that ships with the toolchain can be uclibc though, that
is perfectly fine. Build it and have a look at the result as I think it
will be fine.
Cheers,
Richard
prev parent reply other threads:[~2012-10-29 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 14:28 uclibc sdk issue Giuseppe Condorelli
2012-10-26 19:08 ` Khem Raj
2012-10-29 8:48 ` Giuseppe Condorelli
2012-10-29 10:14 ` Richard Purdie [this message]
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=1351505648.2828.2.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=giuseppe.condorelli@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox