3. Known bugs/misfeatures

X11 compilation sometimes stop without a reason when you're using Gnome-terminal as your terminal emulator.

workaround: Run SDK from xterm terminal emulator (we don't know what is the significant different between
these terminal emulators, but that fixes it). For example to run SDK in a login shell, use this:

$ xterm -ls -e /scratchbox/users/$USER/run.sh &

Rxvt and gnome-terminal 2.2.1 have also been reported not to interrupt X11 compilation (the problem has manifested
with gnome-terminal 2.0.1).

Tip: if you differentiate the SDK terminal from your other terminals with colors, you don't accidentally try to
compile software in a wrong window. To get xterm with scrollbar on the right, 256 line buffer, larger font, black
background with gray text and text effects reversed, add these options: -sb -rightbar -sl 256 -fn 9x15 -bg Black
-fg Gray -rv

Sbrsh (CPU-transparency) daemon on ARM dies sometimes, this should produce following warning:

sbrsh: Can't connect (Connection refused)

workaround: Login to the ARM device and restart sbrshd. Sometimes it's iPAQ that freezes, in that case you
have to boot the iPAQ and restart sbrshd.

/etc/ directories are different in SDK for compilation and on target (because SDK tools need different /etc/ files
from the SW compiled for the target).

workaround: copy required files from /etc/ directory to /targets/[target]/etc/ directory inside the SDK
before running ARM software, or change the software to install and use it's configuration files from /usr/etc/
directory.

On ARM running a program complains about not finding a library that 'ldd' finds for that program, e.g. xterm doesn't
find Xft library. This is related to above problem (/etc/ld.so.cache).

workaround: login to ARM machine (after compiling busybox, so that you have shell there) and run 'ldconfig'
there before running the program, for example: