|
My build of MAMEUI 0.242 doesn't run
#393703 - 04/04/22 05:41 PM
|
|
|
I run your pre-compiled MAMEUI64 and it works fine.
I'm a long time MAMEUI user and I never got any issue with my compilations (subtarget=ARCADE) until version 0.229, when the splash is shown and then bails out.
I have none issues with vanilla MAME subtargets.
For the version 0.229 when this was detected you did say "If you're using GCC 10.2 then that is known behavior. Use an older version such as 10.1", so... In 0.242 are we still with the same scenario? Which toolchain versions (msys, gcc, etc...) are you using?
Please, please, I would like to continue running subtargets...
Thanks
Juanan
|
|
|
|
Re: My build of MAMEUI 0.242 doesn't run
[Re: heartbitt]
#393714 - 04/05/22 02:08 AM
|
|
|
> I run your pre-compiled MAMEUI64 and it works fine.
> I'm a long time MAMEUI user and I never got any issue with my compilations
> (subtarget=ARCADE) until version 0.229, when the splash is shown and then bails out.
>
> I have none issues with vanilla MAME subtargets.
>
> For the version 0.229 when this was detected you did say "If you're using GCC 10.2
> then that is known behavior. Use an older version such as 10.1", so... In 0.242 are
> we still with the same scenario? Which toolchain versions (msys, gcc, etc...) are you
> using?
>
> Please, please, I would like to continue running subtargets...
> Thanks
> Juanan
Since you are getting the source from github, take notice of the warning that is in README.md
You must use GCC 10.1 - later versions will compile but crash at start.
I don't have a suitable debugger (if any exist) or any way of knowing where the crash occurs.
I was planning on doing the upgrade to 11.2 and finding out what the problem is, no matter how long it took, but there's a showstopper - the stack trace doesn't work with 11.2, not even in MAME. So, I'm holding off for a while.
|
|
|
|
Index 
Threaded 
My build of MAMEUI 0.242 doesn't run
Reply
[Re: 