All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: meta-toolchain build for uclibc, possible issue?
Date: Tue, 08 Jan 2013 17:37:38 +0000	[thread overview]
Message-ID: <1357666658.13022.11.camel@ted> (raw)
In-Reply-To: <CAOHjBZuDiLmweStxyu3ghH-WMz6S-TO+R7qDurnrvXHw9x4qvg@mail.gmail.com>

On Tue, 2013-01-08 at 16:12 +0100, Giuseppe Condorelli wrote:
> Hi All,
>  
> gcc-runtime nativesdk is failing due to the lack of libm.
> I want to build meta-toolchain for uclibc, I mean obtaining the cross
> compiler for these flavour, so libm should be
> provided by the uclibc. But repository doesn't build any uclibc for
> nativesdk, (it builds eglibc by default).
> I'm in trouble to understand this, where is the answer I'm not
> understanding?
>  
> Please can you help me?

What are you trying to build *exactly*?

Do you want a toolchain that contains a compiler and uclibc for the
target you're cross compiling for?

or do you want the toolchain itself to use uclibc instead of glibc as
well as whatever the target uses?

The options would be:

a) Uclibc based toolchain, glibc target system
b) Uclibc based toolchain, uclibc target system
c) glibc based toolchain, uclibc target system
d) glibc based toolchain, glibc target system

We only support c/d and only those combinations are known to work.

Its important to differentiate between the C library the cross compiler
links against compared to the C library the ultimate target system uses.

Cheers,

Richard






  reply	other threads:[~2013-01-08 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 15:12 meta-toolchain build for uclibc, possible issue? Giuseppe Condorelli
2013-01-08 17:37 ` Richard Purdie [this message]
2013-01-09  8:30   ` Giuseppe Condorelli

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=1357666658.13022.11.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 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.