All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	klibc@zytor.com, torvalds@osdl.org, akpm@osdl.org
Subject: Re: Merge strategy for klibc
Date: Mon, 20 Mar 2006 21:19:05 +0100	[thread overview]
Message-ID: <20060320201905.GI20746@lug-owl.de> (raw)
In-Reply-To: <441F0859.2010703@zytor.com>

[-- Attachment #1: Type: text/plain, Size: 865 bytes --]

On Mon, 2006-03-20 11:54:01 -0800, H. Peter Anvin <hpa@zytor.com> 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       jbglaw@lug-owl.de    . +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 #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-03-20 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 19:54 Merge strategy for klibc H. Peter Anvin
2006-03-20 20:19 ` Jan-Benedict Glaw [this message]
2006-03-20 21:24   ` H. Peter Anvin
2006-03-20 20:22 ` Al Viro
2006-03-20 21:17   ` [klibc] " H. Peter Anvin
2006-03-20 20:54 ` Ingo Oeser
2006-03-20 22:09 ` Roman Zippel
2006-03-22  0:27   ` H. Peter Anvin
2006-03-22 14:47     ` Antonio Vargas
2006-03-22 16:11       ` H. Peter Anvin
2006-03-21 12:39 ` Michael Tokarev

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=20060320201905.GI20746@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=akpm@osdl.org \
    --cc=hpa@zytor.com \
    --cc=klibc@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.