From: Christian Neukirchen <chneukirchen@gmail.com>
To: musl@lists.openwall.com
Subject: Re: gcc segfault at src/mman/mlockall.c
Date: Sat, 19 May 2012 23:26:11 +0200 [thread overview]
Message-ID: <87wr47lv64.fsf@gmail.com> (raw)
In-Reply-To: <20120518225845.GY163@brightrain.aerifal.cx> (Rich Felker's message of "Fri, 18 May 2012 18:58:45 -0400")
Rich Felker <dalias@aerifal.cx> writes:
> On Fri, May 18, 2012 at 02:51:23PM -0400, Kurt H Maier wrote:
>> On Fri, May 18, 2012 at 08:43:33PM +0200, Jens Staal wrote:
>> > > obase-musl still lacks a lot due to many legacy syscalls musl probably
>> > > won't implement.
>> > >
>> > > --
>> > > Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
>> >
>> > Could libbsd help with those?
>>
>> Is it really worth adding on more and more cruft just to get a base
>> system working? In my opinion it would be better to flesh out sbase[1]
>> or something like it. Requiring a compatibility shim for your core
>> utilities sounds like a bad day waiting to happen.
>
> If there are really _syscalls_ not implemented, I'd be interested in
> knowing what they are.
Sorry, not syscalls; I mean BSD libc functions such as fts(3).
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
prev parent reply other threads:[~2012-05-19 21:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 16:35 Isaac Dunham
2012-05-15 16:42 ` Isaac Dunham
2012-05-15 19:21 ` Szabolcs Nagy
2012-05-15 19:30 ` Szabolcs Nagy
2012-05-16 18:53 ` Isaac Dunham
2012-05-16 22:04 ` Szabolcs Nagy
2012-05-17 6:07 ` Isaac Dunham
2012-05-18 14:58 ` Jens Staal
2012-05-18 17:21 ` Christian Neukirchen
2012-05-18 18:43 ` Jens Staal
2012-05-18 18:51 ` Kurt H Maier
2012-05-18 22:58 ` Rich Felker
2012-05-18 23:13 ` Kurt H Maier
2012-05-19 0:45 ` Isaac Dunham
2012-05-19 0:56 ` Rich Felker
2012-05-19 18:45 ` noXCUse, userspace options Isaac Dunham
2012-05-24 6:16 ` noXCUse grep Isaac Dunham
2012-05-19 21:26 ` Christian Neukirchen [this message]
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=87wr47lv64.fsf@gmail.com \
--to=chneukirchen@gmail.com \
--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).