Quote:
Originally Posted by knc1
Just try rebuilding it for installation on the Kindle.
./configure --prefix=/mnt/us/tcc --sysroot=/mnt/us
should do the trick.
Then, in /mnt/us/tcc/{include,lib} just symlink to wherever lab126 put the files.
That __should__ (according to the tcc docs) fix both the library and the include search paths.
@lab126: My apologies, the use of loader scripts for *.so files was a brain fart of the gnu/gcc project. We will have to let you slide on that one.
|
I did that for SDL, so that programs I compile automatically look for the SDL libraries in /mnt/us/SDL instead of on the root partition. That way you do not need to change LD_LIBRARY_PATH before running an SDL-dependent program.
I tried building the new tinycc sources from the git repository, but I had some technical difficulties with that so I built my tcc package with
lrizzo's tcc build instead, along with header files from multiple sources, and extra scripts, to make it easy to install and use. No matter how you build it, there will be complications caused by broken symlnks and such in various kindle firmware versions, which I have been "fixing" in the install and tccmake scripts.
EDIT: Symlinks take very little space and only two known symlinks are missing from /usr/lib in firmware version 3.3, which is why I RESTORE symlinks in /usr/lib only if they are missing. Moving symlinks elsewhere would create inconsistencies with other firmware versions. Regarding your suggestion to create symlinks in the /mnt/us/tcc folder -- on vfat? 
I am also curious why the "-run" parameter does not work in lrizzo's build of tcc.