This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: Confirming porting strategy
- From: Daniel Jacobowitz <drow at false dot org>
- To: "Jonathan S. Shapiro" <shap at eros-os dot org>
- Cc: libc-ports at sources dot redhat dot com
- Date: Fri, 23 Sep 2005 14:16:10 -0400
- Subject: Re: Confirming porting strategy
- References: <1127498731.3212.81.camel@mikado64.cs.jhu.edu>
On Fri, Sep 23, 2005 at 02:05:31PM -0400, Jonathan S. Shapiro wrote:
> I want to outline our current porting strategy. I suspect it is generic,
> but perhaps we have missed something that someone will be able to point
> out and save us a bunch of time.
It's not generic; if I'm understanding you right, you've already got an
OS and a system libc. Almost all glibc ports are done to systems
without an existing libc. So this:
> 1. All system call stubs return ENOSYS. This is turning out to be
> pretty easy, since it is what the generic/ tree does.
is a complete non-starter; in fact, I'd do it the other way around, and
have the system calls first. Higher level libc behavior is much
simpler to analyze and debug.
--
Daniel Jacobowitz
CodeSourcery, LLC