review, please!

Mark M. Kettenis kettenis@wins.uva.nl
Tue Feb 2 01:04:00 GMT 1999


The paragraph starting with *BUT* contained some spelling mistakes.  I
also changed the wording a bit to make it somewhat easier to
understand.  This is my proposal:

   *BUT*: updating the C library is no trivial task and it is very easy
   to damage one's system.  Therefore, persons who do not exactly know
   what to do, should consider using a binary distribution instead, when
   they become available.  All major Linux distributors will hopefully
   base their next release on glibc 2.1.  Don't tell us you haven't been
   warned.  Another reason why not everybody should think about compiling
   glibc is disk and CPU requirements: on Intel platforms the full build
   requires about 290MB plus the space you need to install it.  This
   number is probably higher on RISC platforms.  Compiling takes more
   than 4 hours on a i586@133, and still 45 minutes on a 2xi686@233.  See
   the FAQ file for more numbers.

The 4+ hours for a i586@133 is probably a bit conservative but that's
probably fine since the goal is not to encourage people too much.

As far as bugreports are concerned.  I volunteer to deal with
Hurd-specific bug-reports.  

And don't forget to reenable sending bug-reports to bugs@gnu.org again :-).

Mark



More information about the Libc-hacker mailing list