View Single Post
Old 05-28-2012, 08:31 PM   #151
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
You could probably force specific libraries to load first with -L, but there are already two known missing symlinks (and probably more), and the version numbers depend on which kindle firmware (tccmake works on DX/DXG/K3/K4/K5). Also, tccmake only supports script parameters $1 through $9, so for more parameters it would need to loop and shift. The more libraries you force, the less modules you can link, without adding complexity to the script.

When I searched for a solution to this problem (tcc only having PARTIAL support for the "ld scripting language"), the forums that discussed this problem called this a "library loader script" and I just continued to use that existing terminology. Because the solution that I used worked, I did not have to RTFM, so I did not learn the "right words" to call these things.

But even though tcc does not support all four ld scripting keywords, that is not the problem here. The real problem is that the old ld script points to a missing static link library, and tcc complains that it cannot find the library that the old "ld control script" pointed to. My simplified version removed the reference to the missing file (which may cause problems with static linking, but we are solving these problems as the need arises and that has not yet been a problem).

I just use tcc for testing simple stuff, and I use codesourcery for the final binary executable, which runs many time faster in most cases.

Last edited by geekmaster; 05-28-2012 at 08:35 PM.
geekmaster is offline   Reply With Quote