Quote:
Originally Posted by ross
That's usually because an executable is compiled for the wrong architecture. 'file' can tell you which arch something was built for:
src/rxvt: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.14, not stripped I got rxvt-2.7.10 to build with: source /usr/local/poky/eabi-glibc/arm/environment-setup
./configure --host=arm-poky-linux-gnueabi
make I didn't try it on emulator/device though. Even with display updates fixed, you'de still need to get the keyboard to pop up somehow (since matchbox-keyboard hooks into GTK to know when to show/hide). |
Damn that's the tip I wanted...
It seems that CC is not taken from the environment so it used the local gcc for X86 (I should have payed more attention when it was building). After I modified the Makefile it worked. (autoreconf gave some errors so I did not use it.)
I am using rxvt-2.6.4 so that might explain the different experience you had.
Now for the good news: IT RUNS (on the emulator using Ctrl-Alt-1 to refresh :-). I need to add some refresh patches. I need to check which ones are working on an X-only app. Hope to post the binary and modified code soon.
... and then ofcourse the keyboard ...