From: Ley Foon Tan <lftan@altera.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Rob Landley <rob@landley.net>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Generic syscall ABI support
Date: Fri, 29 Mar 2013 17:49:59 +0800 [thread overview]
Message-ID: <1364550599.7481.8.camel@leyfoon-vm> (raw)
In-Reply-To: <51551E60.4070708@zytor.com>
On Thu, 2013-03-28 at 21:53 -0700, H. Peter Anvin wrote:
> On 03/28/2013 09:41 PM, Rob Landley wrote:
> >
> > You don't need a new glibc port, you need a new klibc or musl port.
> >
> > http://www.openwall.com/lists/musl/2012/07/08/1
> >
> > Way less work than getting glibc working for your basic smoketest...
> >
>
> Good point. Average time to port klibc to a new architecture is about
> four hours as long as the person porting knows the calling conventions
> and assembly language involved.
>
> -hpa
>
>
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?
Thanks.
Regards
lftan
next prev parent reply other threads:[~2013-03-29 10:05 UTC|newest]
Thread overview: 13+ 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:30 ` Ley Foon Tan
2013-03-28 11:42 ` Arnd Bergmann
2013-03-29 4:41 ` Rob Landley
2013-03-29 4:41 ` Rob Landley
2013-03-29 4:53 ` H. Peter Anvin
2013-03-29 9:49 ` Ley Foon Tan [this message]
2013-03-29 10:42 ` Arnd Bergmann
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=1364550599.7481.8.camel@leyfoon-vm \
--to=lftan@altera.com \
--cc=arnd@arndb.de \
--cc=hpa@zytor.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;
as well as URLs for NNTP newsgroup(s).