Quote:
Originally Posted by cscat
As I said, the terminal runs but I can't type. And yes your awesome programs run here too my friend!
I think I found a catch, here we go:
First I executed the binary file of Joppy Terminal which I took from my KT 5.1.0. It was compiled with TCC v1.6a... So I tried to compile it on my KT 5.0.1 with TCC v1.5 and although it is compiled (it does produce the binary file), but it gives this error:
tcc: file '/usr/lib/libpthread_nonshared.a' not found
I think libpthread and libthread_db were one of the damn additions of KT 5.1.0 (well not sure about that) but they were one of reason I had so much trouble with WAF apps.
|
Just run the tcc installer again to fix that problem.
And like I said SSH from diags uses a different touchscreen event device number. The correct way to use it is to scan for it like I do in my sigcap script. Look up how that works. It works in both main and diags boots which use different touchscreen (zforce) event device numbers...
You did not answer my question. WHICH ssh are you using: main or diags? JoppyTerm (the version I looked at) only works from main unless you change the zforce device number and recompile it (or better yet make it work from both main and diags SSH)...