Thank you for your response.
Quote:
Originally Posted by shamanNS
|
Yes, but there was a problem of it using GCC that was too new.
Later it turned out that combination of static stdlib and flags to disable c++11 ABI would work, but at first, I had to compile using gcc 4.9.4
Quote:
Originally Posted by shamanNS
As for Kindle devices using v5.x firmware branch stuff is usually compiled to target ABI and use certain compiler flags in groups like this:
1) Kindle Touch & PW1
|
These might be out of scope, given they will not be able to get new books soon...
Quote:
Originally Posted by shamanNS
2) PW2 and all later models, all the way to firmware 5.16.2.1.1 ( = the last "soft float" firmware)
|
Do all of those use c++09 ABI? That is not clear. And that is probably the most important part, since my program interfaces with system library and has to feed it strings and maps.
Quote:
Originally Posted by shamanNS
3) armhf ABI / firmware 5.16.3 and later.
|
Same as above, both instruction set and ABI should match, I think. If anything, software FP might still work, I am not too concerned with performance, it is slow as molasses.
Quote:
Originally Posted by shamanNS
So then you have situation that all models released between PW4 and PW6 could be on armel or armhf ABI depending on if the device is on older or latest available firmware for that particular model. Thus the end user needs to know and use correct binaries.
Like, I have a PW5 on 5.16.2.1.1 firmware that I do not want to ever update to newer, armhf firmware.
|
Could you try running the
executables and tell me if any of them work? I have rebuilt them with gcc 10-something and they should represent combinations of el/hf and c++11/legacy. Not sure about library compatibility.