From: user@example.net   
      
   Nikos Chantziaras wrote:   
   > João Jerónimo wrote:   
   >> J.O. Aho escreveu:   
   >>   
   >>> You need at least glibc 2.7, all you need to do is to add it to your   
   >>> package.keywords   
   >>   
   >> And pray for it to compile ok.   
   >   
   > It should.  And don't forget that nothing in your system is touched if   
   > it does not compile OK.   
   >   
   > But as always, this is glibc, the most crucial library there is, so...   
      
   There is ways to recover from a bad glibc, a good thing to do, before starting   
   to build it, make a binary tarball with quickpkg. If the new glibc fails to   
   work as it should ater installed (in 99.999% of the cases it will work if it   
   installs), then use an install media, unpack the tarball to your gentoo   
   installation, then chroot to it and install it through portage, this way you   
   get rid of the files that differs between the versions and you have a working   
   glibc again.   
      
   Myself, I have had some bad experience of glibc compiling badly on a RedHat   
   7.3 system and used a bit more trickier way to reinstall glibc.   
      
   --   
      
      //Aho   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)