From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Agenda for next release?
Date: Mon, 31 Dec 2012 23:51:07 -0500 [thread overview]
Message-ID: <20130101045107.GQ20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <1357013172.31232.29@driftwood>
On Mon, Dec 31, 2012 at 10:06:12PM -0600, Rob Landley wrote:
> On 12/31/2012 01:11:31 PM, Rich Felker wrote:
> >Another port (perhaps x32, like originally proposed) is also
> >definitely an option if anybody's up for doing it. I had considered
> >doing it myself in this release cycle, but I'm a bit busy with some
> >other projects for at least a couple weeks so I'd rather not get
> >bogged down in a big time-eater right away, and instead spend my time
> >with musl on small isolated feature additions and bug fixes.
> >
> >Anything else I missed?
>
> From my point of view sh4, sparc32 support are interesting because
> switching aboriginal to musl would either have to drop support for
> those two platforms or support two libcs in parallel. (m68k and
> s390x are of secondary interest becauase those are the platforms
> I've been trying to add. In theory mips64 is currently supported but
> in practice it's deeply flaky at the kernel and possibly qemu level;
> not widely used.)
>
> Not priorities, just thought I'd chip in...
Thanks! And good to see you again! I'd be interested in seeing these
ports too, but like I said above now is not the best time for me to
start doing a new port myself. So unless somebody else wants to try a
shot at it, these will probably have to wait a bit.
Rich
next prev parent reply other threads:[~2013-01-01 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 19:11 Rich Felker
2012-12-31 21:37 ` Brad Conroy
2013-01-01 2:38 ` Rich Felker
2013-01-01 4:06 ` Rob Landley
2013-01-01 4:51 ` Rich Felker [this message]
2013-01-04 7:22 ` Rob Landley
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=20130101045107.GQ20323@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).