MAME Compiler 64 v2.0.197

[Mordwaffe]

Already tried it did get error but since old one still works will use it till I figuere out the new one. The error I got was for python. Earlier I inquired about setting the python,qt, and env bat files and you said it wasn't necessary that MC64 did it internally.

For what it is worth I get the same error with the new tools (20140905) and not the older (20121207).

I can however compile form the command line (not using MC64 to compile, but i did use it to apply the diff) using the new just fine after running the bat files to set the ENV.

[trickyd]

I updated to the new tools when HomeBrew came out (hb won't compile with old tools). Haven't had any fails after running bat files but still miss the ease of MC64

[Mordwaffe]

So what does HB (or groovy for that matter) have that regular mame does not?  I am out of the loop on these alternate builds

[trickyd]

HB has all the hacks you will never see in mame.

[headkaze]

MAME Compiler 64 v1.3.2
- Fix for compiling MAME 0154+

[trickyd]

Thanks for the update

[headkaze]

Mame Compiler 64 v2.0 Released
- UI Update, new options added, auto-download source and patches

[trickyd]

What is the difference between the source folder under the mingw folder and the mame source folder?

[tronyony]

EDIT: This seems to be what fixed my problem.  I have now compiled 137, 149, and 151 via external HDD.  I found this reading the hiscore diff thread.

Posted by B2K24: "try any other drive and don't compile on C:\ 
If you have to buy a USB flash or use external. For me trying to compile on win 7 using C:\ is always problems because some directories have lock icons even with UAC disabled and logged on Admin account."



I know this is a somewhat old thread but I just can't seem to figure this out.  I'm trying to add hi_137 to mame0137s and make it 64bit and I just can't get.  The patch, patches fine but it won't compile.  I have tried, what I believe to be, everything.  I'm running Windows 8 on a Mac via Bootcamp.  I have tried MC64 v2.0 with the newest mgwin, MC64 v1.17 with the same mgwin as well as an older mgwin (201001020), and MrDo's way.  all with random errors.  From what I've read, I need to use MC64 v1.17 and mgwin 20100102.  Am I doing something wrong or missing something?  Here is what I get with MC64 v1.17 and the newest mgwin and older mgwin:

Compiling Mame64...
Using Parameters  MSVC_BUILD=1 PTR64=1
process_begin: CreateProcess(NULL, uname -a, ...) failed.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
makefile:94: *** Unable to detect TARGETOS from uname -a: .  Stop.


Thank you in advance for looking.

V/r
Tony

[ramos8414]

Does this work with mame 0.157?

[milhouse]

Is anyone else having a problem with MinGW?  I downloaded the package from mame but am getting  data errors for a bunch of files in the 7-zip pacage when it tries to self-exract.

[tronyony]

Is anyone else having a problem with MinGW?  I downloaded the package from mame but am getting  data errors for a bunch of files in the 7-zip pacage when it tries to self-exract.

I didn't have issues with MinGW.  Maybe try a different web browser?


V/r
Tony

[EMDB]

Version 0.157 compiled just fine with Mame Compiler 64 2.0 + MinGW MAME 20140905 but version 0.158 doesn't...

Compiling Mame...
Using Parameters -j6 NOWERROR=1 TARGETOS=win32 TARGET=mame OSD=windows PTR64=1
mkdir -p obj/windows64
mkdir -p obj/windows64/build
mkdir -p obj/windows64/emu/audio
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus/centronics
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus/generic
The syntax of the command is incorrect.
make: [obj/windows64] Error 1 (ignored)
mkdir -p obj/windows64/emu/bus/isa
The syntax of the command is incorrect.
make: [obj/windows64/build] Error 1 (ignored)
mkdir -p obj/windows64/emu/bus/neogeo
The syntax of the command is incorrect.
make: [obj/windows64/emu/audio] Error 1 (ignored)
mkdir -p obj/windows64/emu/bus/rs232
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus/scsi
make: [obj/windows64/emu/bus] Error 1 (ignored)
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus/vectrex
make: [obj/windows64/emu/bus/centronics] Error 1 (ignored)
The syntax of the command is incorrect.
make: [obj/windows64/emu/bus/generic] Error 1 (ignored)

...

make: [obj/windows64/osd/windows] Error 1 (ignored)
make: [obj/windows64/tools] Error 1 (ignored)
Assembler messages:
Fatal error: can't create obj/windows64/build/makedep.o: No such file or directory
Assembler messages:
Fatal error: can't create obj/windows64/lib/util/astring.o: No such file or directory
Assembler messages:
Fatal error: can't create obj/windows64/lib/util/corealloc.o: No such file or directory
Assembler messages:
Fatal error: can't create obj/windows64/lib/util/corefile.o: No such file or directory
src/lib/util/corealloc.c:384:1: fatal error: error writing to -: Invalid argument
 }
 ^
compilation terminated.
Assembler messages:
Fatal error: can't create obj/windows64/lib/util/unicode.o: No such file or directory
make: *** [obj/windows64/lib/util/corealloc.o] Error 1
make: *** Waiting for unfinished jobs....
src/lib/util/unicode.c:345:1: fatal error: error writing to -: No error
 }
 ^
compilation terminated.
src/lib/util/astring.c:483:1: fatal error: error writing to -: No error
 }
 ^
compilation terminated.
src/build/makedep.c:463:1: fatal error: error writing to -: Invalid argument
 }
 ^
compilation terminated.
make: *** [obj/windows64/build/makedep.o] Error 1
make: *** [obj/windows64/lib/util/astring.o] Error 1
make: *** [obj/windows64/lib/util/unicode.o] Error 1
src/lib/util/corefile.c:1052:1: fatal error: error writing to -: No error
 }
 ^
compilation terminated.
make: *** [obj/windows64/lib/util/corefile.o] Error 1
Assembler messages:
Fatal error: can't create obj/windows64/osd/windows/vconv.o: No such file or directory
make: *** [obj/windows64/osd/windows/vconv.o] Error 1
Finished!
0 Hours 0 Minutes and 2 Seconds Elapsed.

[headkaze]

Please download Mame Compiler 64 2.0.1 for the 0.158+ fix

[EMDB]

Please download Mame Compiler 64 2.0.1 for the 0.158+ fix

Thanks. Works like a charm again 

[otsep]

I'm seeing this error when trying to compile 158(WinUI) using 2.0.1.

Windows 7 Pro 64-bit

The src was freshly downloaded before compiling.

Code: [Select]

Compiling src/osd/windows/d3d9intf.c...
Compiling src/osd/windows/drawd3d.c...
Compiling src/osd/windows/drawdd.c...
Compiling src/osd/windows/d3dhlsl.c...
make: *** No rule to make target `obj/winui64/osd/windows/drawbgfx.o', needed by `obj/winui64/libosd.a'.  Stop.
make: *** Waiting for unfinished jobs....
Compiling src/osd/windows/drawgdi.c...
Finished!
0 Hours 7 Minutes and 12 Seconds Elapsed.

Regular MAME 158 compiles fine.

[otsep]

I noticed that MAMEui is now 159.  Could this be the cause?

[otsep]

?

[headkaze]

I noticed that MAMEui is now 159.  Could this be the cause?

Yes the MameUI file does not include a version number to identify it so it doesn't always match the official Mame version in MC64's file list. I have updated the file list so you can download it and try again.

[otsep]

Yes the MameUI file does not include a version number to identify it so it doesn't always match the official Mame version in MC64's file list. I have updated the file list so you can download it and try again.

Thanks headkaze. That took care of it.


Sent from my iPhone using Tapatalk

[machyavel]

Hello and thanks a lot for mame compiler 64. I used it many times but now I'm facing an issue with 2.0.1, trying to compile mame159 with groovy patch.

If possible, please have a look at the log file attached. Error messages start line 2741 :
In file included from z:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/winnt.h:1446:0

Any clue on how to fix this?
Thanks in advance

EDIT: I upgraded MINGW and it works now.

[Jumpstile]

Can someone give me instructions on how to set up the new version of MinGW (the latest version from the GIT) with this compiling software? I can't seem to get it working for some reason... A quick step by step would be helpful, I'm sure, for many here and on the net.

Thank you!!

- J*

[what2be]

I second that suggestion! (and Jumpstile, I just sent you a PM on Hyperspin as well asking this very question)

[headkaze]

I just tested Mame 0.160 with the MinGW version you can download directly from MC64 and it works fine. So I would just use that. I may update to the newer version in the near future.

[bobmoo79]

Deleted.

[gamepimp]

Just downloaded MAME 0.160 source, 0.160 hi score patch, MC 2.0.1, and the MinGW from MC site. Applied the patch without any issues. Started compiling and it looked like things were going well. But after about 8 minutes, the compiling completed with the error messages listed below: 

Finished!
0 Hours 9 Minutes and 54 Seconds Elapsed.
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:950:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:819:1: error: previous declaration of 'long long int _mm_cvtsd_si64x(__m128d)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:951:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:869:1: error: previous declaration of '__m128d _mm_cvtsi64x_sd(__m128d, long long int)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:952:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/xmmintrin.h:595:1: error: previous declaration of '__m128 _mm_cvtsi64x_ss(__m128, long long int)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:953:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/xmmintrin.h:505:1: error: previous declaration of 'long long int _mm_cvtss_si64x(__m128)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:954:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:841:1: error: previous declaration of 'long long int _mm_cvttsd_si64x(__m128d)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:955:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/xmmintrin.h:550:1: error: previous declaration of 'long long int _mm_cvttss_si64x(__m128)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:956:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:1467:1: error: previous declaration of '__m128i _mm_cvtsi64x_si128(long long int)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:957:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:221:1: error: previous declaration of 'long long int _mm_cvtsi128_si64x(__m128i)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:958:5: error: conflicts with new declaration with 'C' linkage
make: *** [obj/windows64/osd/modules/debugger/debugwin.o] Error 1

Any thoughts on what might be going wrong here? Certainly looks like there's an issue with MinGW. But I believe the version of MinGW from the MC site is supposed to work fine with 0.160. I have Windows 7 Pro 64 bit with an i5 processor. I've included a pic of the build options I had selected. Any help is greatly appreciated!

[syncmaster]

Hello
the compile tools have changed once again, so the best way is to wait MC64 to be updated
which is surely on the way with the MAME 0.161 release out

[gamepimp]

Sounds good. I will just hang tight until the next release. Thx!

[Jumpstile]

Haven't been able to compile MAME .161 with the old tools. Hope a fix is in the works for the compiler! Thanks a ton, Headkaze!

 - J*

[Yoeddy1]

Yes, please update asap.  We appreciate the work with this as it makes compiling so easy!

Jason

[Jonny G]

Not able to compile with latest mingw either but also, hi scores don't seem to be working in .160 or .161. I just reverted to .153 and all was fine. Checked my mame.ini and all patches were enabled and hi score directory set correctly. Anyone else getting this?

EDIT - scratch that. Somehow my hiscore.dat had gotten deleted.

[headkaze]

I'm currently updating MC64 to support Mame 0161 and the new build tools.

[Yoeddy1]

It looks like an update has been made, but has the process changed?  I'm not sure where I'm going wrong.  Do I need to update compiler tools?  When I download the MAME source, diff file, and compiler tools, I then try to apply the patch, but it errors out. 

Thoughts?

Jason

[Yoeddy1]

Nevermind...I figured it out.  I was trying to apply the patch before the compiling tools were done unzipping.

Thanks,
Jason

[headkaze]

Nevermind...I figured it out.  I was trying to apply the patch before the compiling tools were done unzipping.

Thanks,
Jason

Yeah there are a few issues that need sorting out which is why there has been no official announcement yet.

[Yoeddy1]

Nevermind...I figured it out.  I was trying to apply the patch before the compiling tools were done unzipping.

Thanks,
Jason

Yeah there are a few issues that need sorting out which is why there has been no official announcement yet.

Ok, thanks.  I did get MAME 0.161 to compile and have it working with your latest version.  If there's another version coming, I'll test it as well.

Thanks,
Jason

[Jumpstile]

Boy, it takes much longer to compile with the new tools and MAME Compiler 2.161... well over an hour to compile on an i5 processor... Used to take me 30-45 mins tops.


Nevermind... Problem with AntiVirus. Thanks for the updates and bugfixes, headkaze!

 - J*

[headkaze]

Ok, thanks.  I did get MAME 0.161 to compile and have it working with your latest version.  If there's another version coming, I'll test it as well.

There is a new upload but still nothing official. It should now wait for the extraction to finish before allowing you to exit the download.

I believe there is a problem if you download Mame and MameUI source at the same time and try a MameUI compile. I believe it's because the downloader currently doesn't wait for the previous download to finish zip extraction before going onto the next.

Boy, it takes much longer to compile with the new tools and MAME Compiler 2.161... well over an hour to compile on an i5 processor... Used to take me 30-45 mins tops.

For some reason the "-j" parameter is not working. It specifies the number of parallel jobs to run. If anyone has any idea why or how we can solve this please let me know.

EDIT: I just noticed your edit. I believe there is still a problem with this switch not working. I only see two make processes running when I specified 8 parallel jobs. Can anyone confirm?

[Jumpstile]

When I specify 6 parallel jobs, I get 3 MAKE processes.

I was also wondering - can you add a HBMAME target? I can't compile HBMAME with MAME Compiler as of now. Thanks!

 - J*

[Santo8742]

I'm having all kinds of errors trying to compile. Trying to compile version 0161 with hiscore. Keep getting the attached error. When I try to compile from command line I get the error "python is not available in path". Any ideas on what is causing this and how to fix it?