>[...] That is, of course, *after* I
> manage to get libc6 under 416,361 bytes, the size of the libc5
> library...
Have you checked out what Lineo is doing to libc6? They claim having
reduced it by 50% but I have no idea how easy it is to get their sources,
yet.
>[...] _how_ is libc6 better on a rescue tool? I
> have few specific examples. The only _very_ clear reason is that it is a
> pain for libc6 users to build libc5 executables for tomsrtbt. That, I do
> have a fix for, I will be distributing a foolproof libc5 compilation
> thing.
I'd really like to see a foolproof libc5, newlib or uC-lib compilation kit.
I've played around w/ your libc5 compile kit but are having some problems:
Not all programs compile w/ 'CC=-nostdinc -I.../tomslibc5/... -btomslibc5'
since this adds some include paths before the application gets to add it's
prefered paths. Dosemu is an example of where this is a problem.
I'm using your tomsrtbt distro for my embedded proof-of-concept device.
> Now, I am optimistic that it is doable and worthwhile. Or maybe I'll try
> the Cygnus 'newlib' or write my own libc and call it tomslibc, which might
> actually be easier than fitting a current libc6 on tomsrtbt...
ISTR someone has already prepared a library w/ libc5-libc6 glue logic.
Can't remember where though.
//Bj�rnen.
