Who needs cross-compiling anyway when you can just compile directly on the Pyra (maybe with an external screen and/or keyboard, or using ssh)? That's how many of us do it on the Pandora already; on the Pyra, compiling will take an order of magnitude less time, and big stuff like LibreOffice will already be in the distro, so I don't really see why easy cross-compilation is that important.
I'm not compiling on Pyra. My desktop CPU will still be much faster at compiling than any SoC Pyra ships with. Also, you have to deal with one of these three compromises:
A) Edit over a remote connection which can add noticeable latency even when a network local, particularly over wifi
B) Edit on the Pyra directly and hook up a keyboard, mouse, and monitor to the Pyra which requires those things or a KVM
C) Edit locally on a desktop, but then you have to ssh the files you edit which is a pain. A lot more of a pain than sshing the binary which you can make part of the make step. Also, it adds time between when you edit your source and when you make again which adds up if you're fixing compiler errors. I have a funny habit of writing thousands of lines before I compile them ;p
I went with local compilation on my Chromebook because I primarily got it to dev ARM stuff when away from my desktop. But then I had to deal with a or c above and it got annoying fast. That's probably why I almost always test on the Pandora when I'm at home.