Might be useful also because of some other new features, e.g. memcpy copying backwards (no joke).
On Tuesday 08 February 2011 09:52:55 Paweł Hajdan, Jr. wrote: > It seems that with glibc-2.13 there are some serious compatibility > issues. There are good warnings on the planet > (http://psykil.livejournal.com/340806.html), but not every ~arch user > reads the planet, so how about creating news item with detailed > instructions how to ensure smooth glibc-2.13 update or recover a hosed > system? > > -- Andreas K. Huettel Gentoo Linux developer - kde, sci, arm, tex dilfri...@gentoo.org http://www.akhuettel.de/
--- Begin Message ---Hi, Just for your information, this came up on kde-packagers ml... seems that glibc-2.13 does memcpy backwards under certain circumstances (no joke), breaking broken software even more. We'll probably see some surprises once you place it in the tree... Cheers, Andreas http://article.gmane.org/gmane.comp.lib.glibc.alpha/15278 http://sourceware.org/git/?p=glibc.git;a=commit;h=6fb8cbcb58a29fff73eb2101b34caa19a7f88eba -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/--- Begin Message ---Howdy, Due to the way memcpy() is implemented in some newer glibc [1], users may experience crashes in the KDE imap4 ioslave. Thanks to a patch contributed by a nice person, I have committed a fix to both the 4.5 and 4.6 versions of kdepimlibs. The file in question is kdepimlibs/kioslave/imap4/imap4.cpp The SVN revisions are: kdepimlibs 4.5 => r1216162 kdepimlibs 4.6 => r1216163 You might consider pushing a hotfix for this. Regards, Allen [1] http://lwn.net/Articles/414467 _______________________________________________ Kde-packager mailing list kde-packa...@kde.org https://mail.kde.org/mailman/listinfo/kde-packager
--- End Message ---
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
signature.asc
Description: This is a digitally signed message part.
