knc1,
Thank you for your numerous tips in this and other recent threads!
Based on those , I've listed the following information.
Just to remind, I built taskwarrior on a Debian-Jessie-Armel VM, copied it over to my PW1, but was unable to run it due to GLIBC version errors. The executable worked OK on my PW3( 5.7.4 with GLIBC 2.19) and KT3(5.8.0 with GLIBC 2.19).
Kindle Models and associated Framework and GLIBC versions
Model -- FW version ------------ (e)GLIBC version
KT1 ---- 5.0.0 to 5.3.7.3 ------ 2.12.1
PW1 ---- 5.2.0 to 5.6.1.1 ------ 2.12.1
[But my PW1 has 5.3.6 and 2.10.1
]
PW2 ---- 5.4.2 to 5.6.2.1 ------ 2.12.1
PW2 ---- 5.6.5 to 5.7.4 -------- 2.19
PW3 ---- 5.6.1.1 to 5.8.2.1 ---- 2.19
PW3 ---- 5.8.5 to 5.8.9.0.2 ---- 2.20
[My KT3 has 5.8.0 and 2.19]
Requirement of GLIBC versions by libraries for running on PW1
libgnutls-deb0.so.28: 2.15, 2.17
stdc++.so.6: 2.17, 2.18
libp11-kit.so.0: 2.15, 2.16
So... minimum 2.18
Possible Options:
1. Update Framework version of PW1 from 5.3.6 to 5.6.1.1? but as the above table indicates, this does not push the GLIBC version of the PW1 beyond 2.12.1
2. Compile taskwarrior again on the VM and this time, link older libraries to it?
3. Compile taskwarrior again on the VM and
statically link the older libraries? But this not recommended by the experts.
4. Use patchelf to hack the executable headers? Seems risky...
What would you suggest?