Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
portable libc extracted from OpenBSD
6 views
Skip to first unread message
Goon
Jun 18, 2016, 2:49:43 AM6/18/16
to
Hello,
Some years ago I extracted the memory system from OpenBSD's
libc, I put it on http://goon.yellowcouch.org/software/
Under the name libc.rogue.
This might be useful if you want to make a small
footprint libc. It includes powerpc sys headers.
goon
Some years ago I extracted the memory system from OpenBSD's
libc, I put it on http://goon.yellowcouch.org/software/
Under the name libc.rogue.
This might be useful if you want to make a small
footprint libc. It includes powerpc sys headers.
goon
Tinker
Jun 19, 2016, 12:39:57 AM6/19/16
to
On 2016-06-19 12:36, Johan Ceuppens wrote:
> On Sat, Jun 18, 2016 at 09:36:33PM +0800, Tinker wrote:
>> What would it be used for?
>>
>
> e.g. adding some libc functionality but not the whole thing
> on a OpenBSD powerpc self-built kernel. This then provides
> you with a system.
>
> You can also make something like newlib from it and you can
> change the architecture too if you want by looking up the
> C sys headers in the OpenBSD kernel.
Like an embedded or "microkernel" statically linked with libc and a
program binary and that's all, no root filesystem?
Are you using the full kernel?
Like NetBSD rump?
> On Sat, Jun 18, 2016 at 09:36:33PM +0800, Tinker wrote:
>> What would it be used for?
>>
>
> e.g. adding some libc functionality but not the whole thing
> on a OpenBSD powerpc self-built kernel. This then provides
> you with a system.
>
> You can also make something like newlib from it and you can
> change the architecture too if you want by looking up the
> C sys headers in the OpenBSD kernel.
Like an embedded or "microkernel" statically linked with libc and a
program binary and that's all, no root filesystem?
Are you using the full kernel?
Like NetBSD rump?
0 new messages