Currently, the Dev Extends are causing issues with people who have been using their Pandora a bit.
Essentially, this is because its binding whatever configuration files are present in the extend over your Pandora.
The best way to solve this would be to create your own root overlay, and install the dev tools in there.. or of course, install the dev tools direct to NAND.
I have been testing out various other methods around this, such as compiler GCC in the standard cross-compiler manner, so it can be launched from a PND. However, simple tests worked fine, but complex tests caused it to fail spectacularly.. so that needs figured out a bit. I also don't seem to have the greatest amount of time these days to do fiddling, and seem to be far more tired than usual
I'd therefore advise you not to use the Dev Extends unless you know what you're doing and have backups.. however, I have never marked these things as being terribly stable, and always labeled them as the "dodgy hacks" they are. It's an interesting hack, but its becoming increasingly like something that has to be done uniquely for each Pandora, rather than a generic Dev Extend that works on all - due to the nature of the AUFS binds ( which don't always take.. grrr )
Original post hidden in the spoiler tags.
Edited by Stuckie, 23 August 2010 - 06:21 PM.