> There's absolutely no valid technical reason that glibc in Red > Hat Linux 8.0 should not have been included. It is superior to > glibc 2.2 in numerous ways, including standards compliance, > performance, and also various new features. Every mainstream > distribution will be using glibc 2.3 likely within the next 6 > months, and there's no reason not to. In addition, the other > distributions will benefit greatly from all of the legwork that > has been done by Red Hat, and that includes beta testing, bug > fixing, stabilization, etc.
I do appreciate the work that redhat does, and if their users are willing to be their beta testers and "stabilizers" for glibc, then I do suppose its up to them. > > >I really do see your frustration, as now anyone who develops software on > >redhat (at least those that keep up with redhat) cannot release binaries > >and expect them to work on anyone elses system. You don't need to worry > >about compiling for every system out there, just what is current > >release. > > Sure you can. If you need to build binaries which are compatible > with older glibc, simply compile them using older compat glibc. > It's quite simple actually. Again, don't spread FUD. please, explain, as this has been the whole reason this is come up, tell us how, and we'll all be much happier. > >As far as actually getting this done, redhat has provided cross compiler > >rpms in the past, so you may be able to get these, and cross compile for > >glibc2.2. I don't see a rough time for binary snapshots, just a rough > >time for developers using cvs snapshots of glibc > > A cross compiler is something used to produce binaries for an > architecture other than the architecture the compiler is running > on. Not sure what that has to do with glibc. you can compile gcc against any libc (different versions, different libc's), etc. So, if you compile a gcc against uclibc, and install that, its a cross-compiler. same deal with other versions of glibc > I hope this clarifies any misunderstandings, and misconceptions > that people have about glibc 2.2.9x and glibc 2.3 which is now > officially released. If not, please feel free to discuss the > issue on the glibc mailing lists, where I'm sure all of the glibc > developers would be glad to discuss any concerns people may have. as of 7 hours ago, its time to upgrade ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
