Versatile Arcade Machine Emulator

MAME is an arcade machine emulator covering a broad spectrum of hardware
ranging from the very earliest CPU-based systems to much more modern 3D
platforms. In conjuntion with ROM and CHD images "dumped" from arcade games'
original circuit-board ROM chips, hard disks, and CD-ROMs which are not
included in this package it allows you to play thousands of arcade video games.

Build Results
RPM Lint

Refresh

Source Files

Filename	Size	Changed
_constraints	0000000189 189 Bytes	over 10 years
_link	0000000113 113 Bytes	over 10 years
mame-fix-executable-suffix.patch	0000000327 327 Bytes	over 11 years
mame.changes	0000053813 52.6 KB	over 10 years
mame.ini.in	0000001059 1.03 KB	almost 14 years
mame.spec	0000007926 7.74 KB	over 10 years
mame0153s.zip	0037829714 36.1 MB	over 10 years
mess.ini.in	0000001031 1.01 KB	over 11 years

Revision 13 (latest revision is 20)

gber committed over 10 years ago (revision 13)

- add missing dependency on X11 headers

Comments for mame 8

jobermayr wrote over 10 years ago

Before submitting back please change _constraints to:

jobermayr wrote over 10 years ago

OK, OBS doesn't like tags in comments:

-constraints- -hardware- -disk- -size unit="G">7512

jobermayr wrote over 10 years ago

And killed of some others ...

So please set disk to 8 G and memory to 3 G.

gber wrote over 10 years ago

I don't think you want to set memory constraints since that is RAM+swap, setting physicalmemory to 3GB requires a KVM worker with this much memory to be available. Last time I tried there wasn't and builds were stuck in scheduled state forever, are there now such workers? Also, is there some way I can see the peak of actual memory usage? It seems to have gone down significantly with gold.

jobermayr wrote over 10 years ago

Then we must hope Adrian fixes https://github.com/openSUSE/open-build-service/pull/558 and I am able to reactivate my buildhosts without modifying things all times ...

Btw. requested "memory" != "physicalmemory" ...

gber wrote over 10 years ago

Right, memory might still cause swapping, but if you think it does any good I'll happily put it in. Can you see the peak memory usage? A build with physicalmemory == 1.5G on 64bit succeeded so it should need less than 3G.

jobermayr wrote over 10 years ago

https://pmbs.links2linux.de/package/statistics/home:gber:branches:Games/mame?arch=x86_64&repository=openSUSE_13.1

gber wrote over 10 years ago

Thanks, that's what I was looking for. So the latest build of 0.153 with gold on x86_64 used 1.8GB memory and 8.5GB disk, the last build of 0.151 with bfd ld on x86_64 used 2.8GB memory and 8.1GB so that is quite an improvement. I'll try with disk at 9GB and memory at 2GB which should be enough with gold.