From: Arnd Bergmann <arnd@arndb.de>
To: Ley Foon Tan <lftan@altera.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Rob Landley <rob@landley.net>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Generic syscall ABI support
Date: Fri, 29 Mar 2013 10:42:52 +0000 [thread overview]
Message-ID: <201303291042.52284.arnd@arndb.de> (raw)
In-Reply-To: <1364550599.7481.8.camel@leyfoon-vm>
On Friday 29 March 2013, Ley Foon Tan wrote:
> >
> Thanks for the suggestion.
> Too bad we don't have in-house expert in klibc and musl port.
>
> Hi HPA,
> I knew you are the developer of klibc. Do you have any documentation to
> port a new architecture and also how to replace glibc with klibc in
> build?
>
> By the way, klibc or musl is easier to port?
I have no experience with musl, but klibc is probably the easiest to
port that you can find. Doing a new port doesn't require any prior
knowledge of klibc itself, the code is so small that any experienced
C programmer can understand it entirely in short time and do a new
port. However, it is also not meant as a general purpose libc or a
glibc replacement, as there is a very limited set of code that can use
it. It's certainly complete enough to test that the ABI itself is
working.
Arnd
prev parent reply other threads:[~2013-03-29 10:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 3:09 Generic syscall ABI support Ley Foon Tan
2013-03-28 5:35 ` H. Peter Anvin
2013-03-28 7:44 ` Arnd Bergmann
2013-03-28 8:32 ` Ley Foon Tan
2013-03-28 10:40 ` Arnd Bergmann
2013-03-28 11:30 ` Ley Foon Tan
2013-03-28 11:42 ` Arnd Bergmann
2013-03-29 4:41 ` Rob Landley
2013-03-29 4:53 ` H. Peter Anvin
2013-03-29 9:49 ` Ley Foon Tan
2013-03-29 10:42 ` Arnd Bergmann [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=201303291042.52284.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=hpa@zytor.com \
--cc=lftan@altera.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox