This is an updated version of zsnes. the zsnes project releases once in a while updated versions called "WIPs" with lots more features. Since those are not betas/pre-releases/whatever, and there is no way to tell what the next version will be, I think it would be appropriate to tag the WIPs with _p{date of release}, namely zsnes-1.42_p20060105.ebuild I modified the latest zsnes-1.42.ebuild slightly to point to the new site where WIPs are released. I also got rid of the patch instead of updating it, since it doesn't seem to be needed anymore. One thing that's bugging me though. For zsnes-1.42, gcc outputs 32bit object files before linking them into 32bit zsnes (obviously): # file /var/tmp/portage/zsnes-1.42/work/zsnes_1_42/src/video/hq4x32.o /var/tmp/portage/zsnes-1.42/work/zsnes_1_42/src/video/hq4x32.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped With the WIP though, gcc compiles 64bit objects, and the final result is a 32bit binary after linking # file /var/tmp/portage/zsnes-1.42_p20060105/work/src/video/hq4x32.o /var/tmp/portage/zsnes-1.42_p20060105/work/src/video/hq4x32.o: ELF 64-bit LSB relocatable, AMD x86-64, version 1 (SYSV), not stripped # file /usr/games/bin/zsnes /usr/games/bin/zsnes: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.6, dynamically linked (uses shared libs), stripped Linking gives a bunch of warnings too /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld: warning: i386:x86-64 architecture of input file `video/hq4x32.o' is incompatible with i386 output It doesn't really matter since zsnes works, but I'd be interested if anyone could shed some light on that. Maybe it would be possible to obtain a 64 bit binary also (although I can't), since both gcc and nasm can produce 64bit objects. Someone should test it on x86 to make sure it works too.
Created attachment 78232 [details] zsnes-1.42_p20060105.ebuild
I forgot, WIP stands for "work in progress". They are distributed here: http://www.ipherswipsite.com/
*** This bug has been marked as a duplicate of 109845 ***
well, I just noticed bug 109845. Sorry about that.
