|
|
As far as I can tell, it started somewhere between 0.175 and 0.179.
No matter how I compile, the mame64 executable will send garbage text output to the command line when starting.
It's no big deal, because evertyhing works like it should, but obviously something is not right. The downloadable executable does not do this. I'm using the compiler tools from mamedev, updated and everything.
I've read that others are having this problem as well. Anyone know what this is, and how to fix it?
[ATTACHED IMAGE]
|
|
|
|
Re: Strange issue with compiled MAME 0.180
[Re: Fleskebacon]
#360841 - 12/02/16 01:50 PM
|
|
|
Yeap, I compiled MAME too & it does the same thing. I just didn't really care
|
Windows 11 64 bit OS
Intel Core i7-10700
Nvidia GeForce RTX 2060 6GB
32GB DDR4 RAM
|
|
|
Re: Strange issue with compiled MAME 0.180
[Re: Fleskebacon]
#360855 - 12/02/16 08:58 PM
|
|
|
I attempted to replicate and no issues here on Windows 7 x64.
What is your compile command line? I use the following:
Code:
make -j4 TOOLS=1 SEPARATE_BIN=1 PTR64=1 OPTIMIZE=3 SYMBOLS=1 SYMLEVEL=1 STRIP_SYMBOLS=1 REGENIE=1
I've also followed MAMEdev's instructions for the build environment and ran the following command prior to building .180:
Code:
pacman -Sy
pacman -S bash pacman msys2-runtime --noconfirm --needed
Exit the console and restart Msys2.
pacman -Su --noconfirm
|
|
|
|
Re: Strange issue with compiled MAME 0.180
[Re: Pr3tty F1y]
#360865 - 12/03/16 12:25 AM
|
|
|
> I attempted to replicate and no issues here on Windows 7 x64.
>
> What is your compile command line? I use the following:
> make -j4 TOOLS=1 SEPARATE_BIN=1 PTR64=1 OPTIMIZE=3 SYMBOLS=1 SYMLEVEL=1
> STRIP_SYMBOLS=1 REGENIE=1
>
> I've also followed MAMEdev's instructions for the build environment and ran the
> following command prior to building .180:
> pacman -Sy
> pacman -S bash pacman msys2-runtime --noconfirm --needed
>
> Exit the console and restart Msys2.
>
> pacman -Su --noconfirm
Out of curiosity, what do all of the various parameters after -j4 mean?
|
"Note to Noobs:
We are glad to help you but simply posting that something does not work is not going to lead to you getting help. The more information you can supply defining your problem, the less likely it will be that you will get smart-alec replies.
C.D.~"
|
|
|
Re: Strange issue with compiled MAME 0.180
[Re: Pr3tty F1y]
#360983 - 12/06/16 11:43 AM
|
|
|
I tried different command line options when compiling, but the file I'm currently using was compiled using this:
make -j5 SUBTARGET=arcade STRIP_SYMBOLS=1
I updated the build tools like described.
It's working like it should on my i5 with Win 8.1 x64, but the same file is causing problems on my Core2Duo with Win 7 x64.
It did actually run a couple of times without this happening on the latter as well, but I have no idea why.
|
|
|
|
Re: Strange issue with compiled MAME 0.180
[Re: Envisaged0ne]
#360984 - 12/06/16 11:47 AM
|
|
|
> Yeap, I compiled MAME too & it does the same thing. I just didn't really care
Are you running it on the hardware and os described in you signature?
|
|
|
|
Re: Strange issue with compiled MAME 0.180
[Re: Fleskebacon]
#360988 - 12/06/16 02:32 PM
|
|
|
Yes I am
|
Windows 11 64 bit OS
Intel Core i7-10700
Nvidia GeForce RTX 2060 6GB
32GB DDR4 RAM
|
|
Previous 
Index 
Next 
Threaded 
Strange issue with compiled MAME 0.180
Reply
[Re: 
