>>>>> ">" == Mark Kettenis <[EMAIL PROTECTED]> writes:
>> From: "Davide Libenzi" <[EMAIL PROTECTED]>
>> Date: Mon, 11 Oct 1999 11:51:20 +0200
>> I can confirm that after the installation of glibc-2.1.2 on my Debian system
>> program using C++ iostream always crashes.
>> Please read the documentation that comes with glibc, especially the
>> FAQ (2.27 probably is the solition for your problems). Basically
>> you'll need to recompile the shared libstdc++.
2.27 says (at least my version):
{AJ,CG} If you just upgrade the glibc from 2.0.x (x <= 7) to 2.1,
binaries that have been linked against glibc 2.0 will continue to
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
work.
^^^^
but this isn't true (though I agree that the statement doesn't mention
any C++ lib)
>> It's not a good behaviour coz the libraries has the same main version number
>> ( 2.* and .6 for .so ) and must be binary compatible !
>> And of course it is. Recompilation of binaries is not necessary
>> (except when the programs are explicitly violating the ABI, e.g. when
>> they are using library internals like the __setfpucw function or
>> depend on specific bugs in glibc-2.0 which are now fixed).
>> Recompilation of libraries is necessary in a few cases. Please refer
>> to the FAQ for details.
2.21. What do I need for C++ development?
[...]
{UD} But since in the case of a shared libstdc++ the version numbers should
be different existing programs will continue to work.
Note: I don't have problems with LFS and I did install the "old"
libstdc++ (2.8.0) on the new RedHat (glibc-2.1.1) box, but the simple
(strstreams) test program gets a SEGV...
Bernhard
get my pgp key from a public keyserver (keyID=0x62446355)
-----------------------------------------------------------------------------
Bernhard Heidegger [EMAIL PROTECTED]
Hyperwave Software Research & Development
Albrechtgasse 9/2, A-8010 Graz
Voice: ++43/316/820918-25 Fax: ++43/316/820918-99
-----------------------------------------------------------------------------
