Quote:
Originally Posted by twobob
Got files.
Realised I am too stupid to test them.
What am I doing?
*Reads thread again*
|
OK, so I forgot the install directions.
Presuming you have an ssh connection to your device (K4 ... newer) that is named: kpw
*) unpack archive on PC (probably as root {sudo})
*) find in directory that archive was unpacked into: 'extensions'
*) scp -r extensions kpw:/mnt/us
*) ssh kpw
*) export PATH=/mnt/us/extensions/system/bin:/mnt/us/extensions/system/usr/bin:$PATH
*) now - it should all 'just work' - should not need any LD_LIBRARY_PATH settings (although you can use that if required).
Exception, example that to use new busybox requires the 'busybox arguments' format:
ls --help <<--- see message header? that's the old (soft float) BB
busybox ls --help <<-- check header, that's v-1.22.1 (hard float)
And
lua (or luac) is just lua (luac).
Will work on fixing this busybox build this weekend.
If something seems to go wrong, then:
LD_DEBUG=libs busybox ls --help (or anything else with LD_DEBUG set to something)
should prove interesting.
Also:
LD_DEBUG=libs lua
Will show most of the (new) system libraries being loaded.
lua's internal number type is double, so do some math functions (from libm.so) -
which (if it doesn't blow up) shows that the hard float argument passing is working.
(and just using the interpeter input tests libreadline and libhistory)
Reminder - to exit lua, enter:
os.exit(0)
Note: You will see one Amazon library being loaded: /usr/lib/libenvload.so
That is currently expected and assumed to be harmless.