public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: mjn3@codepoet.org (Manuel Novoa III)
To: Paul Nasrat <pauln@truemesh.com>,
	Robert de Bath <robert$@mayday.cix.co.uk>,
	Riley Williams <rhw@InfraDead.Org>,
	Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: More dev86 changes (0.16.5)
Date: Thu, 25 Jul 2002 10:34:32 -0600	[thread overview]
Message-ID: <20020725163432.GB2577@codepoet.org> (raw)
In-Reply-To: <20020724222631.GA7170@raq465.uk2net.com>

Paul,

On Wed, Jul 24, 2002 at 11:26:32PM +0100, Paul Nasrat wrote:
> I'd quite like to at least attempt to contribute to linux-86/elks libc.
> I've played with ucLibc and also dredged up some stuff in the cvs
> repostiory merged from dev86 but not in dev86 releases, and that confuses
> me...

A little bit of history... uC-libc was the libc put together by the
uClinux people.  It included a lot of dev86 code, but I think that's
where the connection ends.  More than 2 years ago, Erik Andersen forked
a version and renamed it uClibc.  His goal was to have a small libc to
use with busybox.

I got involved with uClibc almost 2 years ago... not long after Erik
had grafted on the glibc headers.  In that time, most of the original
dev86 code in uClibc has been modified or completely replaced.  Of the
current subdirs in uClibc, I've written much of stdlib and most or all
of the code in stdio, string, time, ctype, locale, wctype, and wchar.
Most of that code was written with eventual porting to elks/bcc in mind
and currently builds with the appropriate sys headers.  I'm hoping to
have elks/bcc support in uClibc in the next couple of months.

> It's moved since my last attempt to try and get involved (and failing
> due to slackness)
> 
> http://cvs.uclinux.org/cgi-bin/cvsweb/uClibc/libc/inet/addr.c?rev=1.1&content-type=text/x-cvsweb-markup

uclibc.org is the primary site for uClibc.

> I'd quite like to see dev86 with a cvs repository so I can look over
> different versions to learn about things.  I'd understand if you don't
> want to bother merging past stuff into a repostiory but just out of
> curiosity in terms of compiler stuff, libc stuff, and asm I'd like to
> be able to easily see the stuff you're doing.
> 
> I may not be good enough to contribute, but if you can at least cvs it,
> and give access to that, it'd be an education.

You might also want to look at the busybox cvs repository at busybox.net.
Certainly most of the busybox applets are far more featureful than
their elkscmd counterparts, and many should be easy enough to seperate
out and port to elks.

Manuel

  reply	other threads:[~2002-07-25 16:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-14 14:05 C compiler, assembler and linker Harry Kalogirou
2002-07-14 17:27 ` Manuel Novoa III
2002-07-15  6:07   ` Riley Williams
2002-07-15 17:02     ` Manuel Novoa III
2002-07-15 19:13       ` Riley Williams
2002-07-15 22:02         ` Manuel Novoa III
2002-07-16  6:27           ` Riley Williams
2002-07-17  1:31             ` Manuel Novoa III
2002-07-17  6:33               ` Riley Williams
2002-07-18 12:03                 ` Minix vs. ELKS Feher Tamas
2002-07-18 12:27                   ` Javier Sedano
2002-07-02 15:07                     ` (unknown) Miguel A. Bolanos
2002-07-18 13:40                   ` Minix vs. ELKS Alan Cox
2002-07-22 21:41                 ` C compiler, assembler and linker Robert de Bath
2002-07-23  8:16               ` Robert de Bath
2002-07-23 16:25                 ` Manuel Novoa III
2002-07-23 19:09                   ` Robert de Bath
2002-07-24 21:17         ` More dev86 changes (0.16.5) Robert de Bath
2002-07-24 22:02           ` Riley Williams
2002-07-25 15:42             ` Manuel Novoa III
2002-07-26  7:55               ` Robert de Bath
2002-07-26 15:12                 ` Manuel Novoa III
2002-07-26  8:22             ` Robert de Bath
2002-07-24 22:26           ` Paul Nasrat
2002-07-25 16:34             ` Manuel Novoa III [this message]
2002-07-22 23:26       ` C compiler, assembler and linker Robert de Bath
2002-07-23  0:34         ` Riley Williams
2002-07-23  0:58           ` Manuel Novoa III
2002-07-23  0:46         ` Manuel Novoa III

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=20020725163432.GB2577@codepoet.org \
    --to=mjn3@codepoet.org \
    --cc=linux-8086@vger.kernel.org \
    --cc=pauln@truemesh.com \
    --cc=rhw@InfraDead.Org \
    --cc=robert$@mayday.cix.co.uk \
    /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