MobileRead Forums - View Single Post

hansel · 04-11-2009, 07:20 AM

Sorry for not being very clear... What I mean, as test, is this:

Put your new gtk libs somewhere on the cf, say /mnt/cf/newlibs/
Boot your Iliad in the normal way
Start a ssh to your Iliad an type:

Code:

export DISPLAY=:0.0
LD_LIBRARY_PATH=/mnt/cf/newlibs
/lib/ld-linux.so.2 --list /usr/bin/contentLister

Just to be clear: '/lib/ld-linux.so.2 --list' is an equivalent to the ldd command mentioned by Antartica. It shows what shared libs an executable loads.

If this shows no errors, you can try:

Code:

/usr/bin/contentLister

This will try to run contentLister linked to your new libs... You can use this approach to check all Irex programs (like /usr/bin/displayMgr, /usr/bin/erbusyd, etc) mentioned in start.sh (or your copy thereof)

What I meant by 'logging what happens in start.sh' is this:

At the begin of start.sh add: echo `date` >$HOME/mylog.txt
and after each command in start.sh add: echo "some descriptive text" >> $HOME/mylog.txt

This will result in a file that tells you how far the boot script goes before crashing

04-11-2009, 07:20 AM	#12
hansel JSR FFD2 Posts: 305 Karma: 1045 Join Date: Aug 2008 Location: Rotterdam, Netherlands, Europe, Sol 3 Device: iliad	Sorry for not being very clear... What I mean, as test, is this: Put your new gtk libs somewhere on the cf, say /mnt/cf/newlibs/ Boot your Iliad in the normal way Start a ssh to your Iliad an type: Code: export DISPLAY=:0.0 LD_LIBRARY_PATH=/mnt/cf/newlibs /lib/ld-linux.so.2 --list /usr/bin/contentLister Just to be clear: '/lib/ld-linux.so.2 --list' is an equivalent to the ldd command mentioned by Antartica. It shows what shared libs an executable loads. If this shows no errors, you can try: Code: /usr/bin/contentLister This will try to run contentLister linked to your new libs... You can use this approach to check all Irex programs (like /usr/bin/displayMgr, /usr/bin/erbusyd, etc) mentioned in start.sh (or your copy thereof) What I meant by 'logging what happens in start.sh' is this: At the begin of start.sh add: echo `date` >$HOME/mylog.txt and after each command in start.sh add: echo "some descriptive text" >> $HOME/mylog.txt This will result in a file that tells you how far the boot script goes before crashing Last edited by hansel; 04-11-2009 at 07:25 AM.