WolfMAME binaries for Linux

[mahlemiut]

Now that I'm in a position to easily produce Linux binaries for WolfMAME, I can upload "official" 64-bit Linux binaries, based on SDLMAME.

Right now, I'd like to gauge just how much interest there would be in readily available binaries, or whether I should just save myself the bandwidth and leave to the user to download SDLMAME and the patches, and compile it themselves. I can do 32-bit binaries too, via VMWare, but this isn't able to be fully tested (VMWare is not fast when it comes to games). One day, I'll explore more into building 32-bit apps on a 64-bit system, just not right now.

So, who wants Linux binaries, or is it just a waste of my time?

[The TJT]

Does it work in this?
http://en.wikipedia.org/wiki/Nokia_770

If not...then any idea which mame should I install for that toy?

[mahlemiut]

If it had an x86 or PowerPC (or similar) CPU, then maybe. But I guess it could. I'd doubt you'd get DRC CPU cores working though. You'll be compiling it yourself, too.

[The TJT]

Doesn't sound very promising...

[Chad]

I think the need for linux binaries is probably not a high demmand thing unless you were going to compile binaries for every flavor of linux, because shared libraries are way too picky to compile a one for all type thing. If you could make a static binary of sdlmame for i386, THAT would be the bomb and worth while way more than anything. But, I haven't been able to make static binaries because lack of static libraries for all that sdlmame needs. Compiling 32 on 64 is trivial, add -m32 to the CFLAGS in make (and maybe one libtool change if they haven't fixed that yet). Of course, you'll only be able to run it a 32 bit linux that has the same or very similar shared libraries as the 64 bit you compiled on.

[Alessandro.S]

I only have 32-bit computers at the moment, but will likely have a 64-bit laptop in a few months.

Chad's point is valid, though at the same time WolfMAME binaries could definitely be helpful, and I for one would happily use "official" ones rather than leaving any doubt about my self-compiled ones... or, on the other hand, I could install different distros from the one[s] you're covering and follow your build process to maintain a few more flavors than just one or two.

I'll keep an eye on the thread

[mahlemiut]

Well, here's something to test out. See if there binaires work out.

http://wolfmame.marpirc.net/wolfmame-li ... 27.tar.bz2 (64-bit)
http://wolfmame.marpirc.net/wolfmame-li ... 27.tar.bz2 (32-bit, still using VMWare to do this, can't get it to link correctly under a 64-bit OS, but it will run it)

The only required library for building SDLMAME is SDL 1.2.13, although it may work with versions as early as 1.2.10.
The only other libraries that I am aware that SDLMAME uses are OpenGL, and GTK+ (for the debugger). Maybe something else for -yuvmode also, not sure on that one. I'd figure that since I built it with these available, that the binaries require these installed too.

[Chad]

yum install glibc-devel.i386 libstdc++-devel.i386
yum install SDL-devel.i386 mesa-libGL-devel.i386 libX11-devel.i386 libXinerama-devel.i386

and maybe a few more .i386s to make 32 sdlmame objects link correctly on 64.

now if we could do

yum install glibc-static.i386 libstdc++-static.i386
yum install SDL-static.i386 mesa-libGL-static.i386 libX11-static.i386 libXinerama-static.i386

a universal executable could be made.

[Alessandro.S]

Well, here's something to test out. See if there binaires work out.

http://wolfmame.marpirc.net/wolfmame-li ... 27.tar.bz2 (64-bit)
http://wolfmame.marpirc.net/wolfmame-li ... 27.tar.bz2 (32-bit, still using VMWare to do this, can't get it to link correctly under a 64-bit OS, but it will run it)

The only required library for building SDLMAME is SDL 1.2.13, although it may work with versions as early as 1.2.10.
The only other libraries that I am aware that SDLMAME uses are OpenGL, and GTK+ (for the debugger). Maybe something else for -yuvmode also, not sure on that one. I'd figure that since I built it with these available, that the binaries require these installed too.

Can't bunzip2 the 32-bit one

Code: Select all

[asuardi@sandman wolfmame-linux]$ md5sum wolfmame-linux32-0127.tar.bz2
b8380a3719e4ad35d35ba6d918f2be7e  wolfmame-linux32-0127.tar.bz2
[asuardi@sandman wolfmame-linux]$ bunzip2  wolfmame-linux32-0127.tar.bz2

bunzip2: Data integrity error when decompressing.
	Input file = wolfmame-linux32-0127.tar.bz2, output file = wolfmame-linux32-0127.tar

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

bunzip2: Deleting output file wolfmame-linux32-0127.tar, if it exists.
[asuardi@sandman wolfmame-linux]$ bunzip2 -tvv  wolfmame-linux32-0127.tar.bz2
  wolfmame-linux32-0127.tar.bz2: 
    [1: huff+mtf rt+rld]
    [2: huff+mtf rt+rld]
    [3: huff+mtf rt+rld]
    [4: huff+mtf rt+rld]
    [5: huff+mtf rt+rld]
    [6: huff+mtf rt+rld]
    [7: huff+mtf rt+rld]
    [8: huff+mtf rt+rld]
    [9: huff+mtf rt+rld]
    [10: huff+mtf rt+rld]
    [11: huff+mtf rt+rld]
    [12: huff+mtf rt+rld]
    [13: huff+mtf rt+rld]
    [14: huff+mtf rt+rld]
    [15: huff+mtf rt+rld]
    [16: huff+mtf rt+rld]
    [17: huff+mtf rt+rld]
    [18: huff+mtf rt+rld]
    [19: huff+mtf rt+rld]
    [20: huff+mtf rt+rld]
    [21: huff+mtf rt+rld]
    [22: huff+mtf rt+rld]
    [23: huff+mtf rt+rld]
    [24: huff+mtf rt+rld]
    [25: huff+mtf rt+rld]
    [26: huff+mtf rt+rld]
    [27: huff+mtf rt+rld]
    [28: huff+mtf rt+rld]
    [29: huff+mtf rt+rld]
    [30: huff+mtf rt+rld]
    [31: huff+mtf rt+rld]
    [32: huff+mtf rt+rld]
    [33: huff+mtf rt+rld]
    [34: huff+mtf rt+rld]
    [35: huff+mtf rt+rld]
    [36: huff+mtf rt+rld]
    [37: huff+mtf rt+rld]
    [38: huff+mtf rt+rld]
    [39: huff+mtf rt+rld]
    [40: huff+mtf rt+rld]
    [41: huff+mtf rt+rld]
    [42: huff+mtf rt+rld]
    [43: huff+mtf rt+rld]
    [44: huff+mtf rt+rld]
    [45: huff+mtf rt+rld]
    [46: huff+mtf rt+rld]
    [47: huff+mtf rt+rld]
    [48: huff+mtf rt+rld]
    [49: huff+mtf data integrity (CRC) error in data

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

[mahlemiut]

Re-uploaded, try it this time. Correct filesize is 9,635,707 bytes.

[Alessandro.S]

Thanks Barry, works for me on Fedora 9 x86

[asuardi@sandman wolfmame-linux]$ ./mame -rp /share/roms -playback galaxian.inp galaxian
INPVIEW: using layout type 'standard'
Input file: galaxian.inp
INP version 2.0
Created Tue Aug 26 18:34:07 2008
Recorded using MAME 0.127 [W] (Aug 25 2008)
Average speed: 99.99% (9 seconds)
Total playback frames: 604
Average recorded speed: 99%

[Chad]

64 bit version works on fedora 6 core, decent compatibility range at least for fedora.