It came as somewhat a revelation that linking statically (In the sense that I thought of it) was a real chore (it seemed) when x-compiling for the Kindle. The Kindle has older libraries - really very old in some instances - so being able to embed new function is obviously a bonus and in some cases critical.
Niluje, Knc1 and GM discuss one manifestation of such an issue and it may be too broad a problem to simply say DO THIS. But a collection of CHECK YOU DID THIS will not hurt.
Indeed, to some degree solutions have been found and discussed if only in concept.
Essentially: tips about the correct optimal runtime configuration and potential simple steps to prevent issues surrounding these types of builds are spread apart. It would be good to splat them here or on the wiki eventually.
As a side note:
Given our static complications (Indeed in some cases Codesourcery just fell over) I turned an eye to sets of tools that are alleged and expected to work-out-of-the-box. Other larger concerns would surely have ironed out such issues in a JUST WORK way I reasoned. The main tool I tested was Buildroot and I´ll briefly discuss my - now obvious I suppose, but surprising to me - findings.
After some attempts at full static builds; digging through docs and threads to check I wasn´t doing it wrong; consistent failures; In the end I was coming up with exactly the same issues in buildroot as we were experiencing with full statics.
I finally found THIS THREAD from about a month ago that confirms - and I quote
(The full article discusses relocatable chains - I highlighted the relevant part
Well knock me down with a feather.
I wish I had known that a few moons ago.
So this post is an aide-memoire and hopefully will underline that even the very big fish still are tousling with the self-same problems we little critters are managing to wrestle with - and in the main - win.
So I guess I am simply reserving this space for the moment when we can simply say AH, that old chestnut, just go see the STATIC STATIC thread (or hopefully the wiki and Index by the time you read this thread).
Either way I can report the major tools don´t fare better than the offerings we play with and that is an eye opener for me.
The grass is not always greener. (Although it may have a few more groundskeepers ;) )
Insert Awesome explanations, Typical Fails and miraculous workarounds below. Kindle specific library known issues warmly welcomed.
Please indicate the exact Kindle Model (dx, 3, 5 etc) OS revision and toolchain for best results.
I don´t claim to have any answers but I can see a cohesive place for them would not hurt.
Many thanks.
Niluje, Knc1 and GM discuss one manifestation of such an issue and it may be too broad a problem to simply say DO THIS. But a collection of CHECK YOU DID THIS will not hurt.
Indeed, to some degree solutions have been found and discussed if only in concept.
Essentially: tips about the correct optimal runtime configuration and potential simple steps to prevent issues surrounding these types of builds are spread apart. It would be good to splat them here or on the wiki eventually.
As a side note:
Given our static complications (Indeed in some cases Codesourcery just fell over) I turned an eye to sets of tools that are alleged and expected to work-out-of-the-box. Other larger concerns would surely have ironed out such issues in a JUST WORK way I reasoned. The main tool I tested was Buildroot and I´ll briefly discuss my - now obvious I suppose, but surprising to me - findings.
After some attempts at full static builds; digging through docs and threads to check I wasn´t doing it wrong; consistent failures; In the end I was coming up with exactly the same issues in buildroot as we were experiencing with full statics.
I finally found THIS THREAD from about a month ago that confirms - and I quote
(The full article discusses relocatable chains - I highlighted the relevant part
Quote:
|
Beware however that, if the host systems are different (eg. you build the toolchain on a recent distro, and you move the toolchain to an old distro, or the other way around), you may get problems running the toolchain, as it will depend on the host libraries to run (after all, gcc et al. are just binaries that are linked to the host libraries!). Most notably, the libstdc++ is known to be one of the most common issues. If this is your case, then you may want to build the toolchain entirely staticaly linked. AFAIK, in buildroot, only the crosstool-NG backend can generate such a statically linked toolchain. |
I wish I had known that a few moons ago.
So this post is an aide-memoire and hopefully will underline that even the very big fish still are tousling with the self-same problems we little critters are managing to wrestle with - and in the main - win.
So I guess I am simply reserving this space for the moment when we can simply say AH, that old chestnut, just go see the STATIC STATIC thread (or hopefully the wiki and Index by the time you read this thread).
Either way I can report the major tools don´t fare better than the offerings we play with and that is an eye opener for me.
The grass is not always greener. (Although it may have a few more groundskeepers ;) )
Insert Awesome explanations, Typical Fails and miraculous workarounds below. Kindle specific library known issues warmly welcomed.
Please indicate the exact Kindle Model (dx, 3, 5 etc) OS revision and toolchain for best results.
I don´t claim to have any answers but I can see a cohesive place for them would not hurt.
Many thanks.