glibc api stability: move to SO answer

This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-03-03 00:00:00 +00:00
parent 8b3b0453a6
commit 65d53b9297

View File

@@ -355,10 +355,7 @@ We can also test our hacked glibc on <<user-mode-simulation>> with:
I just noticed that this is actually a good way to develop glibc for other archs. I just noticed that this is actually a good way to develop glibc for other archs.
In this example, we got away without recompiling the userland program because we made a change that did not affect the glibc ABI. TODO: find the best list of ABI stability rules available: In this example, we got away without recompiling the userland program because we made a change that did not affect the glibc ABI, see this answer for an introduction to ABI stability: https://stackoverflow.com/questions/2171177/what-is-an-application-binary-interface-abi/54967743#54967743
* https://plan99.net/~mike/writing-shared-libraries.html
* https://stackoverflow.com/questions/2171177/what-is-an-application-binary-interface-abi
Note that for arch agnostic features that don't rely on bleeding kernel changes that you host doesn't yet have, you can develop glibc natively as explained at: Note that for arch agnostic features that don't rely on bleeding kernel changes that you host doesn't yet have, you can develop glibc natively as explained at: