mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: musl@lists.openwall.com
Subject: Re: ELLCC has self hosted.
Date: Sun, 20 Oct 2013 16:05:52 -0500	[thread overview]
Message-ID: <1382303152.1974.218@driftwood> (raw)
In-Reply-To: <526409B7.3090607@gmail.com> (from agentprog@gmail.com on Sun Oct 20 11:49:59 2013)

I'd cc: the relevant parties but this mailing list is misconfigured  
with the broken reply-to: tag so I'd have to dig through the backscroll  
to find out who they are. Oh well.

On 10/20/2013 11:49:59 AM, agent wrote:
> 19.10.2013 05:02, Richard Pennington ?????:
>> The clang/LLVM based ELLCC project (http://ellcc.org), after having  
>> reached a huge milestone (http://ellcc.org/blog/?p=231) has now  
>> successfully compiled itself.
>> 
>> The steps were:
>> 1. Use gcc to build the compiler with Linux standard libraries.
>> 2. Use ecc to build itself with libc++, libc++ABI, libunwind, musl,  
>> and compiler-rt
>> 3. Use the newly built compiler to build itself again.
...
>> 
>> That is very cool.
>> 
>> -Rich
>> 
> 
> I understand my question is rather stupid, but what is the most  
> preferable way to
> use ecc as a compiler to build itself? Even if I set cc and cxx  
> variables in the
> root configure script, it still builds everything with gcc. Is  
> setting CC and CXX
> environment variables sufficient?
> 
> Dmitry

My question is even dumber: why does the ellcc.org download page say  
the last release was a year ago?

Rob



  reply	other threads:[~2013-10-20 21:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 23:02 Richard Pennington
2013-10-20 16:49 ` agent
2013-10-20 21:05   ` Rob Landley [this message]
2013-10-21  5:27     ` agent

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=1382303152.1974.218@driftwood \
    --to=rob@landley.net \
    --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).