View Single Post
Old 05-23-2012, 10:22 AM   #105
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
Quote:
Originally Posted by deep View Post
Just a note !

The version of /lib/libpthread.so actually worked for me ... so I copied it over to the tcc folder as required by your modified script...
Ahh... I forgot to post the contents of my replacement loader script. Here is the one-line contents of my /mnt/us/tcc/tcc.libpthread.so:

GROUP ( /lib/libpthread.so.0 )

Are you saying that the original loader script works if copied to the tcc folder? That does not make sense to me because the original contains the file reference shown in the tcc error message. It would be nice to know how many different versions of 5.1.0 firmware are out in the wild. How can amazon even support this mess?

EDIT: It looks like JoppyFur and others did not have this problem. Only SOME versions of the 5.1.0 firmware have this problem.

Last edited by geekmaster; 05-23-2012 at 10:27 AM.
geekmaster is offline   Reply With Quote