Re: glibc-2.1.91: segfault problem overcome via kludge

[Andreas Jaeger <aj at suse dot de>]

>>>>> Adam J Richter writes:

Adam,

please send your comments to libc-alpha@sourceware.cygnus.com - I've
set a CC and Reply-To.  The testers of 2.1.91 will most probably not
read your comments on bug-glibc.
 > 	I have overcome the segfaulting problem that I reported
 > earlier tonight by installing each of the .so files with convoluted
 > shell command.

 > 	As far as I can tell, the problem was due an incompatibility
 > between versions of at least one of the .so files that glibc comprises.
 > The problem occured when the new ld-linux.so.2 and libc.so.6 have been
 > installed, but the other .so files have not yet been installed.
Can you describe the problem better?  What exactly is wrong?  What
needs to be fixed in glibc?

 > 	It is likely that others who build glibc from source but
 > do not track the CVS version will experience the same problem.
 > So, to save everyone time, I have created a binary tar file of
 > the glibc that I rebuilt in the standard way after having done
 > a kludged install.  It is:

 > ftp://ftp.yggdrasil.com/private/adam/glibc-2.1.91.x86.tar.gz

 > 	Any Linux/x86 user running glibc-2.1.3 or earlier who
 > wants to install glibc-2.1.91 from source should do something like
 > the following before doing "make install":
 > 	cd /
 > 	tar xfpvU glibc-2.1.91.x86.tar.gz
 > 	ldconfig

 > 	Note that both the "U" flag in tar and the ldconfig command
 > are vitally important to avoid having an unusable system.  The "U"
 > flag will cause tar to remove files before writing them, so as not
 > to kill the running tar program as its own shared libraries are
 > overwritten.  ldconfig will actually switch to the new libraries.

 > 	After that, it should be safe to build and install the new
 > glibc-2.1.91 from source (you can build without doing an install
 > either before or after installing these binaries).

Please note that we strongly advise against installing 2.1.91 as your
primary libc.  Installing 2.1.91 is not safe at all in the moment!

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de