14. Questions and Answers - FAQ

This chapter tries to give answers to questions, that arrived during the installation process. It is not complete, but I will try to update it frequently.

14.1 Common FAQ

• I cannot find a file .bashrc in the roots directory.
  Just copy the files .profile and .bashrc from your user home directory to the root home directory.
• ping to the internet is not working
  to be described
• Lost some necessary files (e.g. /usr/bin directory)
  While working on your installation, it sometimes happens, that you loose some really necessary files (if you are as stupid as I am :((! ). In this case, there is no other chance, than to reflash the root file- system.

  To do this, reset your iPAQ and press the calender-button to reach the boot> prompt. Enter partition define root 0x100000 0xf00000 16 there if you have a 16MByte version (as described in the familiar flash guide). After a params save the flash is cleared and you can start the installtion by entering load root and send the familiar-complete.jffs via the rx protocol.

  Go on with the normal installation procedure described above. see Installation of familiar

• Installed familiar unstable, network does not run out of the box
  The bootstrap.jffs2 of the new familiar system has nearly no pcmcia-network card modules included. Load the module for your card from handhelds.org to your host and follow the instructions in Manual Installation of ipkgs
• PCMCIA sources not compilable (errors finding headers)
  Maybe you did forget to compile and install the kernel modules ? Kernel compilation

14.2 KDevelop FAQ

• kdevelop complains finding libz during arm configure
  Make sure LD_LIBRARY_PATH is set correct. Add -I/usr/local/arm-linux/include to your CPPFLAGS (Program/Options/CompilerOptions). see also kdevelop
• kdevelop complains finding libqte during arm configure
  Make sure the qte-arm lib is compiled and the link (e.g. </usr/lib/qt2arm is correctly set. see also kdevelop
• kdevelop complains finding libqpe during arm configure
  Make sure the qpe-arm lib is compiled and the link (e.g. </usr/lib/qpearm is correctly set. see also kdevelop
• kdevelop prints a lot of errors while linking string with error messages related to libjpeg
  The reason is a bug in kdevelop. The program always configures /usr/lib/libjpeq, which leads to an arm incompatibility linking this lib later. As I did not find out a proper way until now, I relink /usr/lib/libjpeg.so to the arm-libjpeg for the compilation process manually (or with a script).
  Attention !!!make sure to relink back to x86 libjpeg after ready with arm compilation, because you will have strange result otherwise compiling for x86. so jpeg extension for qt
• your program needs additional (user defined) libraries (arm)
  Add -I/where/your/includes/are to your CPPFLAGS (Program/Options/CompilerOptions). Add -l yourlib to your Linker options (Program/Options/LinkerOptions) line and make sure your self defined lib is located in a standard dir. If not (e.g. arm-lib dir) add -L/where/your/libs/are to your LinkerOptions (Program/Options/CompilerOptions). see also kdevelop
• kdevelop claimes x11Event/setX11Data as missing in a user library(arm)
  The user library is probably not compiled using -DQT_QWS_IPAQ and -DQT_QWS. The main reason is, that your makefile does not use $(OPTIONS) in the compiler flags.