>
> Here's what I think is going on. I bet you are getting KDE from the
> Cooker. I would suggest, since your both running 7.2, that you get it
> from kde.org instead. The reason for this is that the latest libstdc++
> (2.96) doesn't carry a symlink over from 2.95.
Yes. But, please, note, that both gcc-2.95 and gcc-2.96 create compatibilty
link
libstdc++-libc6.1-1.so.2 => current version.
gcc-2.95 specs:
ln -sf libstdc++-3-libc6.2-2-2.10.0.so libstdc++-libc6.1-1.so.2
ln -sf libstdc++-3-libc6.2-2-2.10.0.so libstdc++-libc6.1-1.1.so.2
ln -sf libstdc++-3-libc6.2-2-2.10.0.so libstdc++.so.2.9
gcc-2.96 (current) specs:
STDCV=`echo $RPM_BUILD_ROOT%{_prefix}/lib/libstdc++-libc6*-2.so.3 | sed
's/^.*\(libc6.*-2\).*$/\1/'`
ln -sf libstdc++-$STDCV.so.3 %buildroot/%_libdir/libstdc++-libc6.1-1.so.2
Is there any reason why gcc-2.96 does not create compatibility link for
libstdc++-libc6.1-2.so.3? After all, even after full update I may have
programs that still depend on all library and cannot be recompiled for
whatever reason.
Everything on the Cooker
> needed for a fresh installation looks for libstdc++libc6.2-2.so.3 instead
> of libstdc++-libc6.1-2.so.3.
Yes, I do install 6.2-2, no problem. But why should update remove 6.1-2?
BTW KDE/Qt is actually not important here. It was just an example. Anyway,
after updating to cooker XFree-4.0.2 (after having 4.0.2 from unsupported) my
X run much more nicely so I do want to update to coooker KDE in hope to get
better desktop. I already have 2.1Beta2 from unsupported.
-andrej
