On Mon, 2006-03-20 11:54:01 -0800, H. Peter Anvin <[email protected]> wrote: > a. There are several architectures which don't have klibc ports yet. > Since I don't have access to them, I can't really do them, either. > It's usually a matter of an afternoon or less to port klibc to a > new architecture, though, if you have a working development > environment for it. I haven't yet looked at your code, but what actually needs to be done? Defining syscall macros? I'd probably give it a try for VAX. MfG, JBG -- Jan-Benedict Glaw [email protected] . +49-172-7608481 _ O _ "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
Attachment:
signature.asc
Description: Digital signature
- Follow-Ups:
- Re: Merge strategy for klibc
- From: "H. Peter Anvin" <[email protected]>
- Re: Merge strategy for klibc
- References:
- Merge strategy for klibc
- From: "H. Peter Anvin" <[email protected]>
- Merge strategy for klibc
- Prev by Date: Re: [PATCH] scm: fold __scm_send() into scm_send()
- Next by Date: Re: Merge strategy for klibc
- Previous by thread: Merge strategy for klibc
- Next by thread: Re: Merge strategy for klibc
- Index(es):
 |