From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc-0.9.30.3-rc1
Date: Tue, 02 Mar 2010 21:38:41 +0100 [thread overview]
Message-ID: <87iq9ev4q6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <29ad16f61003020918q282ddabfmfe2b3730783194b4@mail.gmail.com> (Sergey Yakoushkin's message of "Tue, 2 Mar 2010 20:18:09 +0300")
>>>>> "Sergey" == Sergey Yakoushkin <sergey.yakoushkin@gmail.com> writes:
Sergey> Hello,
Sergey> I?m working on tool chain for embedded processor. I?m would like to
Sergey> use uClibc and buildroot.
Sergey> However, my tool chain is based on LLVM compiler (llvm.org).
Sergey> I?ve adopted buildroot scripts for LLVM-GCC (C compiler with gcc
Sergey> front-end and llvm back-end).
Sergey> Ideally I would prefer to compile uClibc using clang (clang.llvm.org)
Sergey> and build complete LLVM based tool chain using buildroot.
Sergey> Are there any plans to support LLVM/clang in buildroot/uClibc?
Not that I'm aware of. If you manage to get uclibc built using llvm,
then you can probably use the external toolchain support we alredy have
in buildroot without too much trouble.
You might want to take a look at crosstool-ng for toolchain building
support/automation.
http://ymorin.is-a-geek.org/projects/crosstool
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-03-02 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100220182228.GN30265@mx.loc>
[not found] ` <4B8D0758.907@digi.com>
[not found] ` <87mxyqvfuo.fsf@macbook.be.48ers.dk>
2010-03-02 17:18 ` [Buildroot] uClibc-0.9.30.3-rc1 Sergey Yakoushkin
2010-03-02 20:38 ` Peter Korsgaard [this message]
2010-03-03 3:34 ` Sergey Yakoushkin
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=87iq9ev4q6.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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