From: Rich Felker <dalias@libc.org>
To: Pedro Giffuni <pfg@FreeBSD.org>
Cc: musl@lists.openwall.com
Subject: Re: FreeBSD's Google Summer of Code 2016
Date: Sat, 5 Mar 2016 16:25:17 -0500 [thread overview]
Message-ID: <20160305212517.GK9349@brightrain.aerifal.cx> (raw)
In-Reply-To: <56DB3D70.8010601@FreeBSD.org>
On Sat, Mar 05, 2016 at 03:11:28PM -0500, Pedro Giffuni wrote:
> Hello;
>
> Just thought I'd point this out in case there are students looking
> for a summer project (paid by Google):
>
> In FreeBSD we are always open to alternatives. For this GSoC we
> would consider someone willing to work on a musl port.
>
> https://wiki.freebsd.org/SummerOfCodeIdeas#Port_musl_libc
>
> For such a port you obviously have to have love for the C language
> and specific skills (version control, knowledge of the build system,
> UNIX/syscall knowledge), but I think it may very well be a fun
> project for the right person.
>
> We generally ask for very detailed proposals and it certainly
> would help if you get to try FreeBSD before considering a
> proposal, The process is competitive so we are interested
> in your background.
>
> We are aware musl is centered around linux but just as someone
> managed to port glibc to FreeBSD we think it should be possible
> to make a port clean port of musl. This project would only make
> sense if the code is upstreamed, so at some stage we would also
> appreciate support from musl developers.
>
> For applying you should follow the standard procedure with Google.
> https://summerofcode.withgoogle.com/how-it-works/
Nice!
From our side (musl), the biggest obstacle when people have looked at
doing such a port in the past seems to be missing syscalls, especially
futex and related functionality. For that reason, up til now,
FreeBSD's Linux syscall layer has seemed more functional, and a better
basis for musl-on-FreeBSD, than the native syscall layer. I think a
viable proposal needs a solution to this problem on the kernel side --
perhaps exposing some of these syscalls that are Linux-emulation-only
now in the native API?
Rich
next prev parent reply other threads:[~2016-03-05 21:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 20:11 Pedro Giffuni
2016-03-05 21:25 ` Rich Felker [this message]
2016-03-05 22:41 ` Pedro Giffuni
2016-03-05 23:32 ` Rich Felker
2016-03-06 0:14 ` Pedro Giffuni
2016-03-06 0:25 ` Rich Felker
2016-03-06 0:31 ` Rich Felker
2016-03-06 1:11 ` Pedro Giffuni
2016-03-06 0:59 ` Pedro Giffuni
2016-03-06 1:08 ` Rich Felker
2016-03-07 8:32 ` Felix Fietkau
2016-03-07 13:06 ` Szabolcs Nagy
2016-03-07 14:22 ` Pedro Giffuni
2016-03-07 13:10 ` Pedro Giffuni
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=20160305212517.GK9349@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=pfg@FreeBSD.org \
/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).