Quote:
Originally Posted by langelgjm
As it turns out my problem (sh not finding a file) was due to the luajit binary pointing to a non-existing program interpreter.
This was solved by linking /lib/ld-linux-armhf.so.3 to /lib/ld-linux.so.3 (which itself was already linked to /lib/ld-2.5.so).
However, now when attempting to run luajit I get a segmentation fault, which is probably going to be beyond my ability to debug, so I think I may try the older version.
|
Just build luajit against a compatible (older) libc