View Single Post
Old 07-28-2017, 12:34 PM   #13
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by zaoqi View Post
Debian 9 ("stretch") — current stable release
That is too new, you will have compatibility problems with the system libraries.

Even the newest firmware build, for the newest generation of Kindles, only uses GLIBC-2.20:
Ref:
https://www.mobileread.com/forums/sh...4&postcount=24

The system library used for Debian 9 is GLIBC-2.24:
Ref:
https://packages.debian.org/stretch/libc6

Translation:
Symbols are versioned.
If you create a program that requires any symbols more recent than GLIBC-20, it will not run on a Kindle.
Unless you provide those newer symbols in a library that you create yourself and use it to 'extend' the older version of the system library that is pre-installed.

If what you built runs on a Kindle, consider yourself lucky, because that is what happened, you got lucky.

Note:
It is real hard to create a 'C' language program without a reference to memcpy.
And memcpy changed at GLIBC-2.14.
Any system with an older version of the system library will be unable to provide that symbol.
Now take another look at my list of what devices / what firmware versions provide which GLIBC versions.
knc1 is offline   Reply With Quote