From: Felix von Leitner <felix-dietlibc@fefe.de>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] klibc requirements
Date: Wed, 9 Jan 2002 15:15:14 +0100 [thread overview]
Message-ID: <20020109141514.GF2510@codeblau.de> (raw)
In-Reply-To: <20020108192450.GA14734@kroah.com> <20020109042331.GB31644@codeblau.de> <20020109045109.GA17776@kroah.com>
In-Reply-To: <20020109045109.GA17776@kroah.com>
Thus spake Greg KH (greg@kroah.com):
> > > - portable, runs on all platforms that the kernel currently
> > > works on, but doesn't have to run on any non-Linux based OS.
> You didn't address this. What are the future plans of porting dietLibc
> to the platforms that are not currently supported by it (but are by
> Linux)?
We will attempt to port the diet libc to every Linux platform that we
have access to. I won't go out and buy hardware to port my software to,
so if anyone needs the diet libc ported somewhere, I need an account on
a test box somewhere.
We are currently missing sh-linux, ia64-linux and m68k-linux and
probably a few architectures that I have never heard of ;)
> It was sent and received on the dietlibc mailing list on Jan 04, 2001.
> It looks like the mailing list archive for the mailing list doesn't have
> any messages for Jan, 2001, otherwise I would point you at it. I can
> forward it to you offline if you want me to.
Please do so!
Felix
next prev parent reply other threads:[~2002-01-09 14:15 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 19:24 [RFC] klibc requirements Greg KH
2002-01-08 20:37 ` Erik Andersen
2002-01-09 4:23 ` Felix von Leitner
2002-01-09 4:34 ` initramfs programs (was [RFC] klibc requirements) Greg KH
2002-01-09 6:10 ` Greg KH
2002-01-09 7:23 ` H. Peter Anvin
2002-01-09 9:33 ` Kai Germaschewski
2002-01-09 10:00 ` Erik Andersen
2002-01-09 4:51 ` [RFC] klibc requirements Greg KH
2002-01-09 5:01 ` H. Peter Anvin
2002-01-09 6:09 ` Greg KH
2002-01-09 7:26 ` H. Peter Anvin
2002-01-10 6:30 ` Rusty Russell
2002-01-10 18:41 ` H. Peter Anvin
2002-01-10 15:24 ` Matthias Kilian
2002-01-10 17:13 ` H. Peter Anvin
2002-01-09 14:15 ` Felix von Leitner [this message]
2002-01-09 14:30 ` Lars Brinkhoff
2002-01-09 14:51 ` Erik Andersen
2002-01-09 10:38 ` initramfs programs (was [RFC] klibc requirements) Anton Altaparmakov
2002-01-09 15:56 ` Pavel Machek
2002-01-09 16:04 ` Patrick Mochel
2002-01-09 16:26 ` Greg KH
2002-01-09 16:29 ` Pavel Machek
2002-01-09 16:48 ` Andreas Ferber
2002-01-09 21:15 ` Alex Bligh - linux-kernel
2002-01-09 21:34 ` Anton Altaparmakov
2002-01-09 21:40 ` Greg KH
2002-01-09 21:55 ` Anton Altaparmakov
2002-01-09 22:15 ` Andreas Ferber
2002-01-10 0:25 ` Tom Rini
2002-01-10 0:38 ` Andreas Ferber
2002-01-10 2:42 ` Tom Rini
2002-01-10 14:09 ` Rob Landley
2002-01-10 22:24 ` Tom Rini
2002-01-11 0:15 ` H. Peter Anvin
2002-01-09 22:12 ` Alex Bligh - linux-kernel
2002-01-09 13:23 ` [RFC] klibc requirements Juan Quintela
2002-01-09 14:57 ` Erik Andersen
2002-01-15 3:08 ` Albert D. Cahalan
2002-01-15 11:55 ` Felix von Leitner
2002-01-15 14:54 ` David Lang
2002-01-15 16:15 ` Doug McNaught
2002-01-15 18:06 ` David Lang
2002-01-15 18:36 ` Doug McNaught
2002-01-16 18:36 ` Erik Andersen
2002-01-16 7:50 ` Albert D. Cahalan
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=20020109141514.GF2510@codeblau.de \
--to=felix-dietlibc@fefe.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox