Re:Windows is not a Microsoft Visual C/C++ Run-Time delivery...
by deniska on Saturday April 12, 2014 @06:06AM
(#7577463)
When glibc guys changed memcpy implementation which changed its undefined behavior, it broke Flash Player and Linus got pissed off. Afair they reverted the change.
Re:Windows is not a Microsoft Visual C/C++ Run-Time delivery...
by cesarb on Saturday April 12, 2014 @08:18AM
(#7577643)
IIRC, they later used symbol versioning so that only newly compiled programs get the real memcpy. Older programs get a fake memcpy which simply calls memmove, which is what Flash should have been calling instead of memcpy.
Re:Windows is not a Microsoft Visual C/C++ Run-Time delivery...
by pjc50 on Saturday April 12, 2014 @03:25AM
(#7577240)
You're basically right; there have been a few incompatible changes (eg aout -> elf, glibc 1 -> 2), but I believe that in all cases there was already a version numbering system in place such that both could be present at the same time.
Additionally, all the distros have update and packaging mechanisms. While you can install off disc, Linux is a lot more .. internet native than Windows.
Re:Windows is not a Microsoft Visual C/C++ Run-Time delivery...
by davidgerard on Saturday April 12, 2014 @11:12AM
(#7578042)
The Linux world largely ignores binary compatibility. If you want old binaries to work on Linux, the API this is most achievable with is ... win32. As provided by Wine.
I think the answer is "no" because Linux distros generally recompile the world with each new major standard library version. If any C standard library gurus are reading this, feel free to chime in!