Please illustrate how you would make an Android system fit with a compiler toolchain, given the number of tools you'd have to change.
Consider specifically the permissions and security model, how you plan to accomodate installing required packages and build managers on an Android. Also consider that the use case for Android is battery
The use case for Android's process model is heavily based around the concept of ephemeral processes that fit into the "app" perspective. Saying you want to run Eclipse on your tablet is no more feasible in
today's world than saying you want to do program development in your browser. (Maybe you do, but it's not realistic to say it's quite possible yet..)
While I don't disagree that maybe everything will change, and eventually Android will become a "Linux on a tablet" distro, that's not how it works today. Just try for yourself thinking about how you would port those programs over to Android, and see what problems you run into. Then consider that when you are doing development, you usually need root privileges. Sure, you can get these on hacked distros, not vanilla Android.
If you disagree, please try to show how your use cases of desktop apps on Android (which, in my mind, implies you misunderstand Android's design) makes sense, and how you would solve these problems.
(The converse also holds, many Android apps don't make sense to run on a desktop..)