Troubleshooting

Here are some commons mistakes during setting up the overlay and compile environment. If nothing described here helps, please visit the Found bugs section and file a ticket for your problem.

• If you have linking problems, package try links with host libraries, not cross check that you use correct cross-fix-root
• When getting the following errer during cross-compiling a package, make sure you performed step 8 of the cross-compiling guide.
  Check if /usr/share/crossdev/include/site/arm-linux-gnueabi exists and is linked to that overlay file correctly.

  checking whether setpgrp takes no argument... configure: error: cannot check setpgrp when cross compiling
  

• You must use same python for host and target. And both versions must be from our overlay. Ensure with eselect that the version is used for real and not only installed.
• if you have some problems with cross compiling start from checking that /usr/armv4tl-softfloat-linux-gnueabi/etc/bash/bashrc exists. If don't you don't did step 7 from Cross compilation correctly.
• Don't forget that the kernel on your gadget could be configured with ANDROID_LOW_MEMORY_KILLER on; if some process doesn't work or you see explicit "Killed" message, check out dmesg output (see ticket:217; don't panic, you can configure the killer through /sys/module/lowmemorykiller/parameters/*).To compile sys-devel/gcc and other big packages natively you might need to disable ANDROID_LOW_MEMORY_KILLER and use the default linux OOM killer to succeed.
• If shr-settings says 'dbus is borked' everywhere and nothing (telephony, fso-gpsd, etc) seems to work, you probably have ophonekitd disabled, check it in processes :)