Hi JKR,
first of all I want to thank you for your effort, about month ago I have installed the dd-wrt to my linksys router (with some addons from optware) and later on I wondered if there is something similar for my Airlive. Now thanks to you and your know-how I have a small linux farm at my home

I am using several your addons (I was especially pleased by the python distribution) and migrate apps from Linksys router to Airlive, since I think it makes much more sense. Sorry for wasting your time, but I feel that instead of demanding more and more pre-built addons from you I would prefer to build my own now.
I have some (basic) linux background but I have no experience with cross-compiling at all. To start somewhere, I have followed the instructions "building_the_firmware" (here
http://www.macsat.com/macsat/component/option,com_openwiki/Itemid,66/id,building_the_firmware), It seem to work for me (more or less), but maybe I miss something important (e.g. I am using the MGB100 toolchain since I have not found any for MGB111).
I am trying to compile (e.g. subversion 1.4.6) on VMWare Fedora 4 distro. When I make the [ "./configure" ; "add include to Makefile" ; "make" ; "make install" ] sequence - everything seem ok and working on fedora but when deployed to Airlive it does not work. The shell just says "command not found". It seems to me that I miss some libraries on Airlive as compared to Fedora. According to ldd on fedora there are dependencies to /lib directory, I thought that the only dependencies should point to /opt/i386-linux/lib if everything was ok.
I feel lost a bit, sorry for maybe totally stupid or wrong question, could you, please, describe how you cross-build and especially deploy the binaries? I am doing it by hand now and I am sure it is the most stupid way to do so. Or in case there is some general tutorial on web, I would be thankful for a link.
Thanks in advance and thank you very much for what you have done so far.
Filodej
Not JKR here

but I guess that when you compile the Fedora system still uses the native GCC compiler; i.e. you are not cross compiling at all. If you run the compiled program on Fedora does it work? It shouldn't work but give you an error like 'Bad ELF interpreter'. If the compiled program works under Fedora then you have not cross-compiled it!
For cross compiling you need to export some system settings that tell most Makefiles what compiler to use, what libraries etc...
For the MGB100 the following works fine:
---
export CC = i386-linux-uclibc-cc
export CXX = i386-linux-uclibc-c++
export LD = i386-linux-uclibc-ld
export AR = i386-linux-uclibc-ar
export AS = i386-linux-uclibc-as
export STRIP = i386-linux-uclibc-strip
export RANLIB = i386-linux-uclibc-ranlib
export NM = i386-linux-uclibc-nm
export CFLAGS='-I/opt/i386-linux/include -Os'
export LDFLAGS=-L/opt/i386-linux/lib
export OBJCOPY = i386-linux-uclibc-objcopy
export OBJDUMP = i386-linux-uclibc-objdump
export ARCH=i386
export CROSS_COMPILE=/opt/i386-linux/bin/i386-linux-uclibc-
export PATH=/opt/i386-linux/bin:$PATH
---
Put this in a text file (called for instance 'cc-settings' on your Fedora system and from the system prompt - before compiling - enter:
source cc-settings
This command will make these settings global.
Also keep in mind that most Makefiles tend to set their own variables, so check the Makefile and make sure that it doesn't contain a setting like:
CC=GCC
because that will set the compiler back to the native compiler...
Also check in the Makefile for the setting of the LD variable. Some Makefiles set it back to the wrong set of libraries.
With me most of the times it helps to just comment out any setting for CC, LD, RANLIB, CFLAFGS and LDFLAGS.
(LD is the linux linker.)
Hope this helps.
Ernst
(Who struggled with this also but has compiled some apps, but not so many as JKR; it is amazing that something like Python can be made to work on this small box.)