Alvin Wong

If i use the -march=armv5te and -mtune=xscale the compiling process fails earlier, looks like it's discontinued. Yes, you'll need to find the last gcc version that supportd this architecture. Also, do you have a mail/social network where I can contact you? I believe I've included my email address in the mail reply I sent you via the sourceforge mail form, but if you haven't got it you should be able to find my email address from my commits in the git repo (just check git log).

Actually, a cross-compiler targetting the Linux ABI might still work, but I don't really remember the details on this.

I've also modified the compile parameters in config.mk to work with newest compilers (-march=armv5te and -mtune=xscale now looks deprecated, replaced those with -marm). I don't think that's correct. -marm pairs with -mthumb and are used with switching between generating ARM code and THUMB code (two different instructions set for ARM architectures). I believe you should keep the -march=armv5te -mtune=xscale parameters as they specify the microarchitecture and available instructions of the target processor,...

... It's been over 4 years and no update at all, you should be able to guess the answer... I still have the device, but nope I have no interest in jumping into this again. It's too underspeced to do anything useful with Android.

Well obviously. I believe there are a lot more places which need this kind of checking...

Then just always put valid paths? Honestly, it'd be good if there are more sanity...

unable to build DeSmuME under openSUSE

Closed as per user's response