mame @0.203 runtime problem on OSX Sierra

[ReddyKilowatt (Reddy Kilowatt)]

I want to install mame on my Macbook Pro. I've updated macports prior to installing mame.

I've followed these instructions as close as possible wiki:howto/Mame

sudo port install mame

The dependancies were installed without any problems.

--->  Computing dependencies for mame
The following dependencies will be installed:
 jpeg
 libsdl2
 libutf8proc
 lua
 portaudio
 portmidi
Continue? [Y/n]: y
--->  Fetching archive for jpeg
--->  Attempting to fetch jpeg-9c_0.darwin_16.x86_64.tbz2 from
https://packages.macports.org/jpeg
--->  Attempting to fetch jpeg-9c_0.darwin_16.x86_64.tbz2.rmd160 from
https://packages.macports.org/jpeg
--->  Installing jpeg @9c_0
--->  Activating jpeg @9c_0
--->  Cleaning jpeg
--->  Fetching archive for libsdl2
--->  Attempting to fetch libsdl2-2.0.10_0.darwin_16.x86_64.tbz2 from
https://packages.macports.org/libsdl2
--->  Attempting to fetch
libsdl2-2.0.10_0.darwin_16.x86_64.tbz2.rmd160 from
https://packages.macports.org/libsdl2
--->  Installing libsdl2 @2.0.10_0
--->  Activating libsdl2 @2.0.10_0
--->  Cleaning libsdl2
--->  Fetching archive for libutf8proc
--->  Attempting to fetch libutf8proc-2.4.0_0.darwin_16.x86_64.tbz2
from https://packages.macports.org/libutf8proc
--->  Attempting to fetch
libutf8proc-2.4.0_0.darwin_16.x86_64.tbz2.rmd160 from
https://packages.macports.org/libutf8proc
--->  Installing libutf8proc @2.4.0_0
--->  Activating libutf8proc @2.4.0_0
--->  Cleaning libutf8proc
--->  Fetching archive for lua
--->  Attempting to fetch lua-5.3.4_2.darwin_16.x86_64.tbz2 from
https://packages.macports.org/lua
--->  Attempting to fetch lua-5.3.4_2.darwin_16.x86_64.tbz2.rmd160
from https://packages.macports.org/lua
--->  Installing lua @5.3.4_2
--->  Activating lua @5.3.4_2
--->  Cleaning lua
--->  Fetching archive for portaudio
--->  Attempting to fetch
portaudio-19.20161030_0.darwin_16.x86_64.tbz2 from
https://packages.macports.org/portaudio
--->  Attempting to fetch
portaudio-19.20161030_0.darwin_16.x86_64.tbz2.rmd160 from
https://packages.macports.org/portaudio
--->  Installing portaudio @19.20161030_0
--->  Activating portaudio @19.20161030_0
--->  Cleaning portaudio
--->  Fetching archive for portmidi
--->  Attempting to fetch portmidi-217_1.darwin_16.x86_64.tbz2 from
https://packages.macports.org/portmidi
--->  Attempting to fetch portmidi-217_1.darwin_16.x86_64.tbz2.rmd160
from https://packages.macports.org/portmidi
--->  Installing portmidi @217_1
--->  Activating portmidi @217_1
--->  Cleaning portmidi
--->  Fetching archive for mame
--->  Attempting to fetch mame-0.203_0.darwin_16.x86_64.tbz2 from
https://packages.macports.org/mame
--->  Attempting to fetch mame-0.203_0.darwin_16.x86_64.tbz2.rmd160
from https://packages.macports.org/mame
--->  Installing mame @0.203_0
--->  Activating mame @0.203_0
--->  Cleaning mame
--->  Updating database of binaries
--->  Updating database of C++ stdlib usage
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  No broken ports found.

but mame did not begin compiling, as indicated here "he installation of the port requires you to compile it. That takes VERY long time, so when you install it take a hot tea, a bag of cookies and wait for it to finish."

no error messages, no prompts, what am I supposed to do?

I've tried running mame64, my screen goes blank and nothing else happens. I have to hold down the power button and reboot.

[jmroot (Joshua Root)]

The wiki page seems to be a bit outdated, as your output indicates that the mame port was installed from a binary archive, not built from source. There was no problem installing it; from what you describe the problem is with running it.

[jmroot (Joshua Root)]

Adding some people who have worked on the port to Cc.

[rubendibattista (Ruben Di Battista)]

Mmmh, @ReddyKilowatt can you give some details on your system? Like macOS version and which machine (e.g. MacBook Pro Late 2011).

A first trial could be forcing Macports to compile it natively on your system. Just try to sudo port -s install mame, this should trigger the build instead of installing it via the binary archive.

[mf2k (Frank Schima)]

I see the same issue on Mojave. But I have no idea what to do about it.

[mf2k (Frank Schima)]

Actually, following the instructions in the wiki page works for me. Particularly the section about creating the directory:

~/mame

and cd'ing into it before running. Did you do that part?

[rubendibattista (Ruben Di Battista)]

I just tried the port again... And it works as expected on Mojave. Without more details on the system it's gonna be difficult to understand why on your pc it does not work...

[mf2k (Frank Schima)]

No feedback from reporter.