From: Erik Andersen <andersen@codepoet.org>
To: Theodore Tso <tytso@mit.edu>,
Juan Quintela <quintela@mandrakesoft.com>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, felix-dietlibc@fefe.de
Subject: Re: [RFC] klibc requirements, round 2
Date: Wed, 16 Jan 2002 11:40:36 -0700 [thread overview]
Message-ID: <20020116184036.GB32184@codepoet.org> (raw)
In-Reply-To: <20020110231849.GA28945@kroah.com> <m2r8ovjpey.fsf@trasno.mitica> <20020114125433.A1357@thunk.org>
In-Reply-To: <20020114125433.A1357@thunk.org>
On Mon Jan 14, 2002 at 12:54:33PM -0500, Theodore Tso wrote:
>
> In any case, given that e2fsprogs is already portable to NetBSD and
> Solaris (the latter so I can run purify to catch memory errors), it
> shouldn't be particularly difficult to get e2fsprogs to run on some
> other alternative libc.
It works just fine with uClibc.. Both shared and static,
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2002-01-16 18:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 23:18 [RFC] klibc requirements, round 2 Greg KH
2002-01-10 22:29 ` Bjorn Wesen
2002-01-11 0:04 ` Greg KH
2002-01-11 0:44 ` Tom Rini
2002-01-11 13:31 ` Felix von Leitner
2002-01-12 12:21 ` Erik Andersen
2002-01-13 1:43 ` Alexander Viro
2002-01-13 2:10 ` Felix von Leitner
2002-01-11 21:46 ` David Lang
2002-01-12 20:16 ` Juan Quintela
2002-01-13 1:38 ` Alexander Viro
2002-01-14 17:54 ` Theodore Tso
2002-01-14 21:57 ` Oliver Xymoron
2002-01-14 23:58 ` Andreas Dilger
2002-01-15 1:26 ` Oliver Xymoron
2002-01-15 3:48 ` Andreas Dilger
2002-01-15 4:05 ` Oliver Xymoron
2002-01-15 17:28 ` Rob Landley
2002-01-16 4:01 ` Alexander Viro
2002-01-16 17:54 ` Oliver Xymoron
2002-01-15 0:33 ` H. Peter Anvin
2002-01-16 18:40 ` Erik Andersen [this message]
2002-01-13 3:58 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2002-01-11 1:50 Torrey Hoffman
2002-01-11 3:32 ` Tom Rini
2002-01-11 6:53 ` H. Peter Anvin
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=20020116184036.GB32184@codepoet.org \
--to=andersen@codepoet.org \
--cc=felix-dietlibc@fefe.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quintela@mandrakesoft.com \
--cc=tytso@mit.edu \
/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