Previous Thread
Next Thread
Print Thread
#110225 - 07/08/17 12:25 PM Look like I having a issue with the msys64 tools.  
Joined: Apr 2006
Posts: 583
Dullaron Offline
Senior Member
Dullaron  Offline
Senior Member

Joined: Apr 2006
Posts: 583
Fort Worth, TX.
cd C:\msys64\src\mame
git pull -f

SET CONFIG_ARCHITECTURE=x64
call C:\msys64\win32\env.bat
DEL /S /Q C:\msys64\src\mame\mame64.exe
DEL /S /Q C:\msys64\src\mame\mame64.sym
RD /S /Q C:\msys64\src\mame\build
make -j5 OPTIMIZE=3 SYMBOLS=1 SYMLEVEL=1 STRIP_SYMBOLS=1 REGENIE=1 TOOLS=1
RD /S /Q C:\msys64\src\mame\build
DEL /S /Q C:\msys64\src\mame\castool.exe
DEL /S /Q C:\msys64\src\mame\floptool.exe
DEL /S /Q C:\msys64\src\mame\imgtool.exe
DEL /S /Q C:\msys64\src\mame\jedutil.exe
DEL /S /Q C:\msys64\src\mame\ldresample.exe
DEL /S /Q C:\msys64\src\mame\ldverify.exe
DEL /S /Q C:\msys64\src\mame\ledutil.exe
DEL /S /Q C:\msys64\src\mame\nltool.exe
DEL /S /Q C:\msys64\src\mame\nlwav.exe
DEL /S /Q C:\msys64\src\mame\pngcmp.exe
DEL /S /Q C:\msys64\src\mame\regrep.exe
DEL /S /Q C:\msys64\src\mame\romcmp.exe
DEL /S /Q C:\msys64\src\mame\split.exe
DEL /S /Q C:\msys64\src\mame\src2html.exe
DEL /S /Q C:\msys64\src\mame\srcclean.exe
DEL /S /Q C:\msys64\src\mame\unidasm.exe

I past these into the win32env cmd screen.

Sometimes it stop or freezing from running. Using the msys64-2017-02-05.exe. I don't know why it does that. Anyone else having this issue?


Windows 10 Pro 64-bit / Intel Core i5-4460 3.20 GHz / 8.00 GB RAM / AMD Radeon R9 200 Series
#110226 - 07/08/17 12:55 PM Re: Look like I having a issue with the msys64 tools. [Re: Dullaron]  
Joined: May 2009
Posts: 1,593
Just Desserts Offline
Very Senior Member
Just Desserts  Offline
Very Senior Member

Joined: May 2009
Posts: 1,593
Originally Posted by Dullaron
Sometimes it stop or freezing from running.


In this order:

1. Check your CPU temperature to make sure you're not overheating.
2. Scan your hard drive and check its SMART settings to make sure it isn't starting to develop corruption.
3. Run memtest86 to make sure your RAM is still OK.

#110227 - 07/08/17 02:56 PM Re: Look like I having a issue with the msys64 tools. [Re: Dullaron]  
Joined: Apr 2006
Posts: 583
Dullaron Offline
Senior Member
Dullaron  Offline
Senior Member

Joined: Apr 2006
Posts: 583
Fort Worth, TX.
I will try j3 to see it go ok with it. j5 might be over work it.


Windows 10 Pro 64-bit / Intel Core i5-4460 3.20 GHz / 8.00 GB RAM / AMD Radeon R9 200 Series
#110228 - 07/08/17 03:38 PM Re: Look like I having a issue with the msys64 tools. [Re: Dullaron]  
Joined: Jan 2012
Posts: 726
rfka01 Offline
Senior Member
rfka01  Offline
Senior Member

Joined: Jan 2012
Posts: 726
Bavaria
Dullaron, your list of commands makes no sense to me ...

- if you want a 64bit build, why do you call it from a 32bit command window?
- if you delete the MAME tools after building anyway, why do you build them in the first place?


Try this:
- In your msys64 directory, call buildtools.bat or conemu.bat
- cd src/mame
- make clean
- git pull
- make -j5

You only need to include TOOLS=1 if you want the MAME tools, and you only need REGENIE=1 if new drivers have been added since your last git pull.

Last edited by rfka01; 07/08/17 03:38 PM.

NCR DMV- DEC Rainbow- Siemens PCD- ITT 3030-Oly People- Acorn A5000- Olivetti M20
#110229 - 07/08/17 05:05 PM Re: Look like I having a issue with the msys64 tools. [Re: Dullaron]  
Joined: Apr 2006
Posts: 583
Dullaron Offline
Senior Member
Dullaron  Offline
Senior Member

Joined: Apr 2006
Posts: 583
Fort Worth, TX.
I only found autorebase.bat and win32env.bat. I couldn't find buildtools.bat and conemu.bat from the msys64-2017-02-05.exe. Those are missing from the msys64-2017-02-05.exe. Maybe someone got those mix up somehow. I don't know why win32env.bat came with these. I do need the chdman.exe file from the tools.

I guest I have to use the Windows Powershell to make then.

Found those in the msys64-2016-02-16.exe. buildtools.bat and conemu.bat Edit: Out of date setup. Won't work.

Last edited by Dullaron; 07/08/17 05:28 PM.

Windows 10 Pro 64-bit / Intel Core i5-4460 3.20 GHz / 8.00 GB RAM / AMD Radeon R9 200 Series
#110230 - 07/08/17 06:13 PM Re: Look like I having a issue with the msys64 tools. [Re: Dullaron]  
Joined: Jan 2012
Posts: 726
rfka01 Offline
Senior Member
rfka01  Offline
Senior Member

Joined: Jan 2012
Posts: 726
Bavaria
Sorry Dullaron ... looks like you're correct. The current archive doesn't seem to contain those anymore.

You only need to use autorebase.bat after the initial installation of your build environment.

Afterwards: Just open win32env.bat, CD to your source directory and build away.

Despite starting from win32env.bat, you get a 64bit build (you've downloaded the 64bit only tools).

I was still building on a toolset manually updated from the February archive, so I hadn't noticed the change.


NCR DMV- DEC Rainbow- Siemens PCD- ITT 3030-Oly People- Acorn A5000- Olivetti M20
#110231 - 07/09/17 12:22 AM Re: Look like I having a issue with the msys64 tools. [Re: Dullaron]  
Joined: Apr 2006
Posts: 583
Dullaron Offline
Senior Member
Dullaron  Offline
Senior Member

Joined: Apr 2006
Posts: 583
Fort Worth, TX.
No problem. smile


Windows 10 Pro 64-bit / Intel Core i5-4460 3.20 GHz / 8.00 GB RAM / AMD Radeon R9 200 Series
#110235 - 07/09/17 12:59 PM Re: Look like I having a issue with the msys64 tools. [Re: Dullaron]  
Joined: Apr 2006
Posts: 583
Dullaron Offline
Senior Member
Dullaron  Offline
Senior Member

Joined: Apr 2006
Posts: 583
Fort Worth, TX.
I don't trust that mame clean. Here why, By the way. I moved MAME folder to C:\.

Might be one of the issues I'm having.

[MINGW64] C:\mame>make clean
GCC 6.3.0 detected
Cleaning genie
Cleaning...
make[1]: Entering directory 'C:/mame/src/devices/cpu/m68000'
Cleaning...
make[1]: Leaving directory 'C:/mame/src/devices/cpu/m68000'

=================================================EDIT.

Look like I got it fix.

Re-downloaded the source to C:\mame. No longer use the C:\msys64\src\mame path. Something was going on in that path.

Also not using the mame clean anymore. Went back to this command instead. RD /S /Q C:\msys64\src\mame\build Safer than sorry.

Anyway no more issues.

Archiving liboptional.a...
Compiling src/mame/mame.cpp...
Building driver list...
Emitting mamevers.rc...
Compiling resources scripts/resources/windows/mame/mame.rc...
34433 driver(s) found
Compiling generated/mame/mame/drivlist.cpp...
Linking mame64.exe...

Pointing out that I gonna start using this command for full clean up. git clean -d -f -X

New setup.

cd C:\mame
git clean -d -f -X
git pull -f

SET CONFIG_ARCHITECTURE=x64
call C:\msys64\win32\env.bat
make -j5 OPTIMIZE=3 SYMBOLS=1 SYMLEVEL=1 STRIP_SYMBOLS=1 TOOLS=1
RD /S /Q C:\mame\build
DEL /S /Q C:\mame\castool.exe; C:\mame\floptool.exe; C:\mame\imgtool.exe; C:\mame\jedutil.exe; C:\mame\ldresample.exe; C:\mame\ldverify.exe; C:\mame\ledutil.exe; C:\mame\nltool.exe; C:\mame\nlwav.exe; C:\mame\pngcmp.exe; C:\mame\regrep.exe; C:\mame\romcmp.exe; C:\mame\split.exe; C:\mame\src2html.exe; C:\mame\srcclean.exe; C:\mame\unidasm.exe

https://sites.google.com/site/o0kinghanco0o/mame_building_info

Last edited by Dullaron; 07/09/17 03:19 PM.

Windows 10 Pro 64-bit / Intel Core i5-4460 3.20 GHz / 8.00 GB RAM / AMD Radeon R9 200 Series
#110251 - 07/11/17 02:37 AM Re: Look like I having a issue with the msys64 tools. [Re: Dullaron]  
Joined: Apr 2006
Posts: 583
Dullaron Offline
Senior Member
Dullaron  Offline
Senior Member

Joined: Apr 2006
Posts: 583
Fort Worth, TX.
Edit: Nevermind I found the files. http://imgur.com/67PWbt1

Why did these commands put the files there? New to me on this behavior. Anyway now I know where the files are. Least the make is working so far.

Last edited by Dullaron; 07/11/17 03:07 AM.

Windows 10 Pro 64-bit / Intel Core i5-4460 3.20 GHz / 8.00 GB RAM / AMD Radeon R9 200 Series
#110255 - 07/11/17 08:28 PM Re: Look like I having a issue with the msys64 tools. [Re: Dullaron]  
Joined: Apr 2006
Posts: 583
Dullaron Offline
Senior Member
Dullaron  Offline
Senior Member

Joined: Apr 2006
Posts: 583
Fort Worth, TX.
OK I found the problem. That win32env.bat from the C:\msys64 folder. If you run make from it. The cmd will get all choke up and then stop the make. It won't go any further than that.

So what I done is copy that win32env.bat over into the C:\mamedev\mame. Rename it to Run.bat.

Paste the commands onto the Run.bat and then save it. Run it from the C:\mamedev\mame. I haven't had an issue at all. Tested 4 times.

Took me a while to find the issue that causing the make to stop. Made a new path and change the commands again. The link have the commands.


Windows 10 Pro 64-bit / Intel Core i5-4460 3.20 GHz / 8.00 GB RAM / AMD Radeon R9 200 Series

Who's Online Now
6 registered members (Bavarese, Pernod, Kale, Duke, TeamE, 1 invisible), 16 guests, and 5 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,412
Posts108,939
Members4,757
Most Online225
May 26th, 2014
Powered by UBB.threads™ PHP Forum Software 7.6.0
Page Time: 0.025s Queries: 14 (0.006s) Memory: 5.0091 MB (Peak: 5.2568 MB) Zlib enabled. Server Time: 2017-09-25 11:23:35 UTC