Messages in this thread | | | From | Rob Landley <> | Subject | Re: [ANNOUNCE] linux-libc-headers 2.6.5.1 | Date | Tue, 4 May 2004 20:49:08 -0500 |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |