bad CPU type in executable: mono32

[irmahs]

I keep getting this error when I try to run RunOnMac.command file.

[Liz4v]

Do you have macOS Catalina (10.15) or later?

[Liz4v]

I was digging a little bit deeper and it doesn't look like it's something I can fix.

mono32 doesn't work on my macOS Catalina. I get that same error you're getting. I thought "no problem, let's just use mono instead then, which is 64 bits."

And I did so, and I get

WARNING: The Carbon driver has not been ported to 64bits, and very few parts of Windows.Forms will work properly, or at all

=================================================================
	Native Crash Reporting
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

and then a crash dump including both native and managed stack traces. Almost no Desktop-Ponies code. Not sure this project can support macOS from now on. :(

[Liz4v]

Root issue seems to be here: https://github.com/mono/mono/issues/6701

[irmahs]

Yeah it seems that 32 bits programs don’t work on the new macOS. I’ll just use it on my Windows. Thank you for programming such a fun application.

On Mon 8 Jun 2020 at 18:28, Ekevoo [email protected] wrote:

I was digging a little bit deeper and it doesn't look like it's something I can fix.

mono32 doesn't work on my macOS Catalina. I get that same error you're getting. I thought "no problem, let's just use mono instead then, which is 64 bits."

And I did so, and I get

WARNING: The Carbon driver has not been ported to 64bits, and very few parts of Windows.Forms will work properly, or at all

================================================================= Native Crash Reporting

Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application.

and then a crash dump including both native and managed stack traces. Almost no Desktop-Ponies code. Not sure this project can support macOS from now on. :(

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RoosterDragon/Desktop-Ponies/issues/28#issuecomment-640735290, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANTWEIFMTUCR2SRVXHKQWRTRVUGRXANCNFSM4NYECFTA .

[Liz4v]

Kudos to RoosterDragon, I only maintain the Mac launcher. 😉

[irmahs]

On Mon 8 Jun 2020 at 18:35, Ekevoo [email protected] wrote:

Kudos to RoosterDragon, I only maintain the Mac launcher. 😉

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RoosterDragon/Desktop-Ponies/issues/28#issuecomment-640738963, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANTWEIFVY7ZNPS66BVZN7FTRVUHMRANCNFSM4NYECFTA .

Respect 😤.

[hidefromkgb]

@yumamri You might want to try my take at MacOS Desktop Ponies.

I`m not certain whether it`ll work (or even compile, for that matter, after that great transition from OpenGL) on anything later than 10.13, but it may be worth giving DPE a try.

[RoosterDragon]

Unclosing per https://github.com/RoosterDragon/Desktop-Ponies/pull/29#issue-431267151 not being a fix.

[Gorness]

Happens for me as well, Big Sur 11.6, Processor Intel Core i5 Dual-Core 2,3 GHz