libc upgrade path (Re: Bug#27334: libc resolver problem solved (critical bug))

[Gergely Madarasz <gorgo@caesar.elte.hu>]

On Wed, 18 Nov 1998, Marcelo E. Magallon wrote:

> * Make a tiny i386-only (other archs don't have this problem) library
>   lib__register_frame_info.so.0 that provides the missing function (where do
>   we obtain this function from? The egcs source?); preload this.

Hmm... now to think about it... do we really need this ? We just have to
make sure all the developers upgrade to something like 2.0.7u-6 or stay at
2.0.7t, so no new binaries get this problem, search for the binaries in
question, submit important bugreports on them, etc... and by the time
slink is released everything should be ok. Anyone experiencing problems
should upgrade to final slink versions... 
Anyway, I would explicitly add a Conflict with current and older
libstdc++2.9, in coordination with the egcs maintainer (release at the
same time), so c++ programs dont break just because they're linked against
the wrong combination of libs.

-- 
Madarasz Gergely           gorgo@caesar.elte.hu         gorgo@linux.rulez.org
      It's practically impossible to look at a penguin and feel angry.
          Egy pingvinre gyakorlatilag lehetetlen haragosan nezni.
                    HuLUG: http://mlf.linux.rulez.org/