Want to Compile Mame 200

[MomoneDk]

Hello Everybody, i want to compile my own Mame 200.
I tried with GCC 7.2, and GCC 8.3, these tools are not working.
I believe that the GCC 8.1 is used to compile this version (wolfmame was compiled with).
Anyone knows where it is possible to download the appropriate tools GCC 8.1 for Mame ? In mamedev this version isn't present.


Thanks

[Phreakwars]

I compile older stuff with Mame Compiler 1.17 which works much better for older versions. I keep a copy of it on my mega account, you can download it from here: Mame_Compiler_117 .exe

[10yard]

Hello Everybody, i want to compile my own Mame 200.
I tried with GCC 7.2, and GCC 8.3, these tools are not working.
I believe that the GCC 8.1 is used to compile this version (wolfmame was compiled with).
Anyone knows where it is possible to download the appropriate tools GCC 8.1 for Mame ? In mamedev this version isn't present.


Thanks

You can download historic build tools from mamedev at https://github.com/mamedev/buildtools/releases/

I recently built all MAME releases in the range 169 to 200 using the GCC 5.3 compiler - that would be version 1.4 from the above releases page.

Good luck.

[MomoneDk]

Thank you for your answers, i will try your solutions.
 

[MomoneDk]

Hello

For 10yard, === > I compiled several mame between 169 and 199 with GCC 5.3 (version 1.4) with no problem.
But Mame 200 compilation gives me always the same error when trying to create "mamearcade.exe" at the end.
The problem is the same with newer GCC on mamedev, with the same error result.
I tried with 2 different PC, one with windows 7, the other with windows 10, always the same error compilation.
I am asking what is the problem......

Not tried Mame Compiler 1.17 yet.

Thanks

[10yard]

Hello

For 10yard, === > I compiled several mame between 169 and 199 with GCC 5.3 (version 1.4) with no problem.
But Mame 200 compilation gives me always the same error when trying to create "mamearcade.exe" at the end.
The problem is the same with newer GCC on mamedev, with the same error result.
I tried with 2 different PC, one with windows 7, the other with windows 10, always the same error compilation.
I am asking what is the problem......

Not tried Mame Compiler 1.17 yet.

Thanks

I compiled again Mame 200 with GCC 5.3 no issues. 
Are you using the default makefile or are you targetting something specific with your build?  Can you post the "user-configurable" section of your makefile here?  Thanks.

[MomoneDk]

Hello

I tried Mame Compiler 1.17, and, of course, as i guessed, it doesn't work, really too old tools to compile Mame 200.

For GCC 5.3.0, 10yard, i don't understand exactly your question, but when i compile the sources of 200, i don't touch/modify the makefile.

Thanks

[Phreakwars]

I feel your pain, I'm in a worse predicament. I'm trying to compile 0.111 for Raspberry Pi and keep failing. Pretty sure either my make file is wrong, or I'm using the wrong tools. I'm using GCC, 0.111 used the MinGW when I compiled that, doesn't work yet, but I know it can be done. Once I get that straight, then I'll have a cool new Pi image that is capable of Ms. Pac-man Hot Pursuit.

[10yard]

Hello

I tried Mame Compiler 1.17, and, of course, as i guessed, it doesn't work, really too old tools to compile Mame 200.

For GCC 5.3.0, 10yard, i don't understand exactly your question, but when i compile the sources of 200, i don't touch/modify the makefile.

Thanks

Ok if you haven't touched your makefile then you could try uncommenting these lines in the file.
REGENIE = 1
NOWERROR = 1

Also do a "make clean" before retrying your make.

[MomoneDk]

Phreakwars, to compile mame 111, with mame compile 1.17 as you do, maybe you know or not, you must edit the "makefile", and remove these words:
-Werror
-Wno-unused-functions

It will compile with no problem.


10 yard, i will try your solution, i hope i will compile with no problem 

[Phreakwars]

Phreakwars, to compile mame 111, with mame compile 1.17 as you do, maybe you know or not, you must edit the "makefile", and remove these words:
-Werror
-Wno-unused-functions

It will compile with no problem.


10 yard, i will try your solution, i hope i will compile with no problem 

I'm trying to get it to run on a Pi/Linux, I tried that already, getting no where. Starting to piss me off. All I ask is a simple 0.111 with the high.diff file added in that runs on a Pi3.. UGH!! I never have problems doing a Windows compile, for some reason I can't get a Pi compile down.. God I suck.

Code: [Select]


#-------------------------------------------------
# compile and linking flags
#-------------------------------------------------

CFLAGS = -std=gnu89 -Isrc -Isrc/includes -Isrc/$(MAMEOS) -I$(OBJ)/layout

ifdef SYMBOLS
CFLAGS += -O0 -Wall -Wno-unused -g
else
CFLAGS += -DNDEBUG \
$(ARCH) -O3 -fno-strict-aliasing \
-Wall \
-Wno-sign-compare \
-Wpointer-arith \
-Wbad-function-cast \
-Wcast-align \
-Wstrict-prototypes \
-Wundef \
-Wformat-security \
-Wwrite-strings \
-Wdeclaration-after-statement
endif

If somebody could PRETTY PLEASE Make me a correct makefile for Raspberry Pi or compile me a build for Pi with the hi_111.diff, I would be forever grateful. My head is rusty these days when it comes to code.

[MomoneDk]

Hello,

10yard, i am really not lucky......
For me and mame 200 it is definitely impossible to compile.
Since the beginning and several attempts, with different pc and gcc, every time i wrote the compilation result, and i have ALWAYS the same error :

Linking mamearcade64.exe...
../../../../mingw-gcc/bin/x64/Release/mame_arcade/liboptional.a(ps2gs.o):ps2gs.c
pp:(.rdata$.refptr._ZTV13device_finderI15ps2_intc_deviceLb1EE[.refptr._ZTV13devi
ce_finderI15ps2_intc_deviceLb1EE]+0x0): undefined reference to `vtable for devic
e_finder<ps2_intc_device, true>'
collect2.exe: error: ld returned 1 exit status
mamearcade.make:252: recipe for target '../../../../../mamearcade64.exe' failed
make[2]: *** [../../../../../mamearcade64.exe] Error 1
makefile:409: recipe for target 'mamearcade' failed
make[1]: *** [mamearcade] Error 2
makefile:1031: recipe for target 'windows_x64' failed
make: *** [windows_x64] Error 2

If anyone have an idea.....

Thanks

[10yard]

Hello,

10yard, i am really not lucky......
For me and mame 200 it is definitely impossible to compile.
Since the beginning and several attempts, with different pc and gcc, every time i wrote the compilation result, and i have ALWAYS the same error :

Linking mamearcade64.exe...
../../../../mingw-gcc/bin/x64/Release/mame_arcade/liboptional.a(ps2gs.o):ps2gs.c
pp:(.rdata$.refptr._ZTV13device_finderI15ps2_intc_deviceLb1EE[.refptr._ZTV13devi
ce_finderI15ps2_intc_deviceLb1EE]+0x0): undefined reference to `vtable for devic
e_finder<ps2_intc_device, true>'
collect2.exe: error: ld returned 1 exit status
mamearcade.make:252: recipe for target '../../../../../mamearcade64.exe' failed
make[2]: *** [../../../../../mamearcade64.exe] Error 1
makefile:409: recipe for target 'mamearcade' failed
make[1]: *** [mamearcade] Error 2
makefile:1031: recipe for target 'windows_x64' failed
make: *** [windows_x64] Error 2

If anyone have an idea.....

Thanks

I believe your error "undefined reference to vtable.." relates to the mame source. 
Might be worth downloading a fresh source from here - https://github.com/mamedev/mame/releases/tag/mame0200

[MomoneDk]

Hello

10 yard, i downloaded the sources from the link you gave me, tried to compile, same error as my last message.....
But, i compiled an old "mamemaster 200" from github that i kept on my pc, and it was a success.....
So, i don't understand where is the error, maybe i will do an "examdiff" between the sources who don't work and the others to see where is the problem (which file is wrong to compile for me).....
But as you never had problems to compile 200, there is nothing to understand.

And, also, i tried to compile the 201 with GCC 5.3, it works, i don't know until which version it works to compile with 5.3.....The compilation is longer thant newer tools, but works.

Thanks

[nitrogen_widget]

Phreakwars, to compile mame 111, with mame compile 1.17 as you do, maybe you know or not, you must edit the "makefile", and remove these words:
-Werror
-Wno-unused-functions

It will compile with no problem.


10 yard, i will try your solution, i hope i will compile with no problem 

I'm trying to get it to run on a Pi/Linux, I tried that already, getting no where. Starting to piss me off. All I ask is a simple 0.111 with the high.diff file added in that runs on a Pi3.. UGH!! I never have problems doing a Windows compile, for some reason I can't get a Pi compile down.. God I suck.

Code: [Select]


#-------------------------------------------------
# compile and linking flags
#-------------------------------------------------

CFLAGS = -std=gnu89 -Isrc -Isrc/includes -Isrc/$(MAMEOS) -I$(OBJ)/layout

ifdef SYMBOLS
CFLAGS += -O0 -Wall -Wno-unused -g
else
CFLAGS += -DNDEBUG \
$(ARCH) -O3 -fno-strict-aliasing \
-Wall \
-Wno-sign-compare \
-Wpointer-arith \
-Wbad-function-cast \
-Wcast-align \
-Wstrict-prototypes \
-Wundef \
-Wformat-security \
-Wwrite-strings \
-Wdeclaration-after-statement
endif

If somebody could PRETTY PLEASE Make me a correct makefile for Raspberry Pi or compile me a build for Pi with the hi_111.diff, I would be forever grateful. My head is rusty these days when it comes to code.

I just checked and advmame 3.9 (106) romset does have the 2x speed-hack.
you have to enable it in the dip switches.
this is on windows but i don't see how there would be a difference.

[Phreakwars]

I just checked and advmame 3.9 (106) romset does have the 2x speed-hack.
you have to enable it in the dip switches.
this is on windows but i don't see how there would be a difference.

Yes, I am aware of that. The reason I'm trying to compile 0.111 is because it was the last version to offer the speedup hack, not the only version clearly, but it was the last. It has a better GUI interface and records on OBS easier. If I wanted just the speedup cheat, I'd use AdvMAME 1.4,  But enough about me, I'll figure out what I'm doing wrong eventually, like I said, I'm a bit rusty. College was over 25 years ago and I've mainly done PHP since then. But I need the practice anyways.