From: Masanori Ogino <masanori.ogino@gmail.com>
To: lowrisc-dev@lists.lowrisc.org
Cc: musl@lists.openwall.com
Subject: [GSoC2016] Weekly Report of Porting musl to RISC-V Project #1
Date: Fri, 27 May 2016 23:02:58 +0900 [thread overview]
Message-ID: <CAA-4+jdfYKC0ufXA-WMb0dc9BmH6JU+Be=4zC012JT-SqUC4Ug@mail.gmail.com> (raw)
Hello,
The coding period of GSoC 2016 began in Monday. Now it's Friday
midnight (in Japan) so I'd like to report the progress on the project.
I forked lluixhi's RISC-V port of musl [1] as written in my proposal,
and applied some patches to catch up with the bleeding edge of the
library. My WIP branch [2] has no significant differences from the
origin in the arch-dependent part for now.
The riscv-gnu-toolchain has been changed to build musl-based
toolchains. Since the master branch of the toolchain has migrated to
GCC 6.1 containing musl support, the integration is straightforward.
If you want to try it, please execute `make musl` after configuration
with my WIP branch [3].
Now I'm working on building a root filesystem with the musl-based
toolchain to test the port and preparing patches to address some
problems I've found. I hope we will be able to launch a Linux system
based on musl on Spike next week.
Any comments would be appreciated. Please tell me your opinion!
Have a nice weekend!
[1]: https://github.com/lluixhi/musl-riscv
[2]: https://github.com/omasanori/musl/tree/riscv
[3]: https://github.com/omasanori/riscv-gnu-toolchain/tree/musl
--
Masanori Ogino
next reply other threads:[~2016-05-27 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 14:02 Masanori Ogino [this message]
2016-05-29 18:14 ` FRIGN
2016-06-03 14:31 ` Masanori Ogino
2016-06-03 14:29 Masanori Ogino
2016-06-03 15:28 ` Szabolcs Nagy
2016-06-03 16:14 ` Masanori Ogino
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='CAA-4+jdfYKC0ufXA-WMb0dc9BmH6JU+Be=4zC012JT-SqUC4Ug@mail.gmail.com' \
--to=masanori.ogino@gmail.com \
--cc=lowrisc-dev@lists.lowrisc.org \
--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).