[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190307160619.GV23599@brightrain.aerifal.cx>
Date: Thu, 7 Mar 2019 11:06:19 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: RISC-V port upstreaming status; Alpine Linux port
On Sun, Jan 06, 2019 at 09:36:31PM -0500, Drew DeVault wrote:
> Hiya folks! I'm a big fan of musl and I've been picking up the work to
> add RISC-V support while I work on porting Alpine Linux to RISC-V.
> I'm basing my work on the last patch we saw on this list, which is also
> mirrored here:
>
> https://github.com/riscv/riscv-musl
>
> I'm pretty confident in the port after writing 3 additional patches
> (some of which address feedback from the previous discussion on this
> list) and integrating another I found sitting on GitHub. You can see all
> four new patches here:
>
> https://github.com/riscv/riscv-musl/pulls
>
> I have a working self-hosted Alpine Linux system based on this port. The
> state of the Alpine port is summarized here:
>
> https://lists.alpinelinux.org/alpine-devel/6377.html
>
> I tried to get in touch with those who put in the intial footwork for
> this port, but haven't been entirely successful so far (and those who
> have responded said they were not able to commit any more time to the
> effort). I'm happy to volunteer to integrate upstream feedback on the
> patchset and take over any additional work necessary to complete the
> upstreaming of the port. What are the next steps?
>
> Thanks for everyone's hard work on this project!
I just posted a followup on https://github.com/riscv/riscv-musl/pull/1
-- right now, things are not in a good state for merging due to mess
with the generic fcntl.h. I'm working through the PRs and commits
there to see if things otherwise look okay now.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
