devkitPro

You don't ordinarily need to call gcc directly like that. Copy the template or one of the example projects to your own directory and run "make" (or build it in programmer's notepad, or whichever IDE you're using if you prefer). Once you've gotten that working, you can start making changes ...

dopefish: 2793-0621-8172

I've ported a handful of applications to the DS using SDL. It's not a good fit. Audio, input, networking, and timers will most likely have to be redone anyway, so those parts of SDL aren't doing you any favors. Which basically just leaves you the video stuff. Using SDL for video on the DS does work ...

Frankly, you should start out with something simple, and work your way up. You're not going to be able to go straight from knowing the basics, to working on an N64 emulator. Especially since emulators tend to be pretty complex, not to mention platform-specific (for performance reasons).

I'm not familiar with it myself, but the library it's complaining about seems to be here:
http://masscat.afraid.org/ninds/debug_stub.php

WinterMute wasn't calling you a novice coder, he was just pointing out that PAlib aims to help novice coders. In fact he didn't say anything about you at all. The problems with PAlib after a new release of devkitARM or libnds generally are due to the poor design of PAlib itself, not because upcoming...