public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Christoph Hellwig <hch@infradead.org>, Mariusz Mazur <mmazur@kernel.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.5.1
Date: Tue, 4 May 2004 20:49:08 -0500	[thread overview]
Message-ID: <200405042049.08742.rob@landley.net> (raw)
In-Reply-To: <20040503194757.A13711@infradead.org>

On Monday 03 May 2004 13:47, Christoph Hellwig wrote:
> On Mon, May 03, 2004 at 01:11:49AM +0200, Mariusz Mazur wrote:
> > Available at http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
> > Changes:
> > - network headers got fixed - most notably removed most common collisions
> > between glibc and llh (I hate making hacks, but don't have much choice -
> > glibc's network headers lack functionality); iproute2 and iputils should
> > build with just small patches (which can be found at the above url) and
> > including linux/{in*,if*} in general should be quite safe now
>
> Maybe someone should spend some time and fix up the glibc headers instead?
> :)

So you think the uclibc users should be getting their headers from glibc then?

I don't.  I like this work, and intend to integrate it into some systems I'm 
putting together, after I get all the rest of the busybox bugs shaken out.  
(Well, not always bugs.  Lots of it's missing functionality.  I'm using 
busybox to replace coreutils, bzip2, findutils, grep, sed, tar, util-linux, 
and so on...  And then adding binutils and gcc and trying to compile software 
with the resultng system.  Yes, I am insane.  This is what's taking up all my 
spare hacking time these days...)

I'll replace glibc with uclibc (and the 2.4 headers with 2.6 headers) once 
I've finished with busybox.  (So far I've had to rewrite sed more or less 
from scratch, and revert to the non-busybox versions of sort, sh, awk, patch, 
ar, gzip, and gunzip.  But some of those are easy to fix, and the rest of 
busybox seems to be capable of being used as part of a development 
environment, even to the point of handling ./configure and make for the GNU 
tools they replace...)

Rob



      parent reply	other threads:[~2004-05-06 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02 23:11 [ANNOUNCE] linux-libc-headers 2.6.5.1 Mariusz Mazur
2004-05-03 18:47 ` Christoph Hellwig
2004-05-03 19:24   ` Kevin P. Fleming
2004-05-03 19:31     ` Christoph Hellwig
2004-05-03 20:05       ` Mariusz Mazur
2004-05-05  1:49   ` Rob Landley [this message]

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=200405042049.08742.rob@landley.net \
    --to=rob@landley.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmazur@kernel.pl \
    /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