From: Richard Pennington <rich@pennware.com>
To: musl@lists.openwall.com
Cc: idunham@lavabit.com
Subject: Re: ELLCC and musl
Date: Mon, 09 Jul 2012 23:31:19 -0500 [thread overview]
Message-ID: <4276283.3PUcmFvR0x@main.pennware.com> (raw)
In-Reply-To: <56982.132.241.65.238.1341885134.squirrel@lavabit.com>
On Monday, July 09, 2012 09:52:14 PM idunham@lavabit.com wrote:
> > I added a blog post making my switch to musl official. :-)
> > http://ellcc.org/blog/?p=135
>
> Neat!
> I have a few questions:
>
> 1-I noticed there was something about beginning a Microblaze port. Out of
> curiousity, is this currently usable (to the point of running cat or ls),
> was it abandoned, or is it present but not yet usable?
The Microblaze port is pretty far along. Most of my library regression tests
succeed.
For executables, I compile and run (NetBSD versions) of cat, chmod, cp echo,
ed, expr, kill, ln ls, mkdir, mv, pwd, rmdir, rm, sleep, and test,
Of these the (rudimentary) tests fail for Microblaze for ed, expr. ls, and
test.
You can see outstanding bugs at http://ellcc.org/bugzilla/
>
> 2-Do you plan to submit patches for mips/ppc (and Microblaze, if you have
> it working) support soon?
> (I ask this partly because Landley says that those two would be enough for
> him to consider moving Aboriginal towards musl. Also, if it would take a
> while and you're willing, some of us could prepare some patches).
Microblaze will probably come before ppc, just because I'm still struggling
with clang/LLVM support of ppc.
>
> 3-Is SVN the only way to download source, or is there a way to get tarballs?
Right now it is just SVN. I could set up tarballs, though, if there is enough
interest.
>
> 4-Roughly what compiler would you expect to be needed to build the
> toolchain? (will GCC-3.4 g++ be enough, or would 4.2 or 4.6 be necessary?)
I have only used clang/LLVM for testing. I was testing against gcc 4.6
previously.
-Rich
next prev parent reply other threads:[~2012-07-10 4:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 13:35 Richard Pennington
2012-07-10 1:52 ` idunham
2012-07-10 4:31 ` Richard Pennington [this message]
2012-07-10 5:10 ` Rich Felker
2012-07-10 6:13 ` Jens Staal
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=4276283.3PUcmFvR0x@main.pennware.com \
--to=rich@pennware.com \
--cc=idunham@lavabit.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).