From: Richard Pennington <rich@pennware.com>
To: musl@lists.openwall.com
Subject: Re: ELLCC update for October 5, 2014
Date: Tue, 07 Oct 2014 11:17:38 -0500 [thread overview]
Message-ID: <54341222.8070400@pennware.com> (raw)
In-Reply-To: <20141007161507.GB1808@newbook>
On 10/07/2014 11:15 AM, Isaac Dunham wrote:
> When you say ELLCC was able to build "itself", are you including just
> LLVM/clang, or also the other parts of the toolchain (musl and binutils)?
ELLCC builds itself. Everything: clang/LLVM, libc++, musl, compiler-rt,
binutils, gdb, and QEMU. All but QEMU are statically linked and self
contained.
-Rich
prev parent reply other threads:[~2014-10-07 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 19:11 Richard Pennington
2014-10-07 16:15 ` Isaac Dunham
2014-10-07 16:17 ` Richard Pennington [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=54341222.8070400@pennware.com \
--to=rich@pennware.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).