Hello all; due to reported mailing-list problems, please CC, as done, to me. And forgive, if I confuse private mail with list-mail... thanks.
Am Dienstag, 22. Januar 2002 19:18 schrieb Charles Steinkuehler: > > >Anyway, I could think of a core that boots without glibc and > > > loads glibc 2.0.7 for floppy releases and glibc whatever for > > > CD, HD et al... > > > > I think supporting 3 different c-libraries at a time will cause > > lots of problems for users, and for the developers supporting > > them. I'd prefer to drop support for the ancient glibc-2.0.7. IMHO we don't need to support 3 or more libraries. The core should boot (and that's what I've proofed to work) with ulibc and will then load glbic-whatever. I've did some work with dachstein 1.0.2 and glibc 2.1.3 and found, that only squid and ez-ipupdate needed a recompile with glibc 2.1.3 (and please note - I don't know what happended with ez-ipupdate, I suddendly had an very old lrp on my CD-image). All of the other apps are working as expected under 2.1.3, even if they are compiled with 2.0.7. And as you see, the apps above are not the one we consider for a floppy release (which is IMHO the "user-space core" in opposite to the "technical boot core"). As another sidenote - once leaf/dachstein allows diffrent glibc-versions, you won't see apps compiled with 2.0.7 anymore - developers will built packages, but they don't have to have an outdated system on the disk to maintain compatability. Being able to boot without glibc and to load libc207.lrp, libc213.lrp or even glibc225.lrp will force developers to use whatever is mainstream among leaf-users, and we will choose the most common determinator, but it is no techinal limitation. > > Can we provide glibc-2.0.7 as a "compatability library", the way > RedHat does, so if necessary, folks can run old code without > worrying about re-compiles or crashes? I'd like to have a system > that could potentially support more than one c library. 2.2.x for > current work, 2.0.7 for older, existing LRP packages, and perhaps > uClibc (or newlib, tinylibc, or similar) for core floppy or > boot-strap features. > Anyone know what details have to be dealt with to have multiple c > libraries on the system at the same time? I don't understand. My proposal is to have busybox statically linked, since it's needed to boot and to load glibcxxx.lrp, from then on you have glibc.xxx.. It's up to the user to choose the apps and libraries on his own needs and responsability. Ok, on a second thought I understand - providing any glibc independently from any other would be straightforward, I have no idea, but if it works on Red Hat.....? kp _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
