OpenXcom Forum
Modding => OpenXcom Extended => OXCE Builds & Ports => Topic started by: m1chael on November 17, 2020, 09:12:51 pm
-
Hi,
I've recently bought a MacBook Air M1 2020 running macOS Big Sur 11.0.1.
I tried to install OXCE v6.7.2 but I was getting an error when I was trying to run it.
I was up and running fine on my older MacBook.
Would you expect OXCE to run on my new laptop? If so, I can post the error message I'm seeing to see if anyone can please offer advice for resolving it?
Thank you
M
-
It was not tested on macOS 11.0 Big Sur... since it's only 5 days old :)
And there are issues when supporting newer macOS versions... with practically each upgrade they stop supporting something... and we need to find out what and fix it.
So it's quite likely that something got broken this time too.
Eventually we will fix it... but it may take a while... I'm kinda afraid now to upgrade my macOS 10.15 Catalina... because if it fails, I won't have any way of creating macOS releases.
If you share the logs, we can try to help...
-
Hmm, I have a MacBook Air from mid 2012... so I can't even upgrade to Big Sur :(
Only MacBook Air 2013+ can be upgraded.
-
If it helps, this is the error message I'm seeing when trying to run it:
Process: openxcom [2343]
Path: /Applications/openxcom.app/Contents/MacOS/openxcom
Identifier: SupSuper.openxcom
Version: ???
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: openxcom [2343]
User ID: 501
Date/Time: 2020-11-26 18:26:05.922 +0000
OS Version: macOS 11.0.1 (20B29)
Report Version: 12
Anonymous UUID: [removed]
Sleep/Wake UUID: [removed]
Time Awake Since Boot: 2500 seconds
Time Since Wake: 160 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [2343]
-
I was able to get it working on my Mac with a workaround using third-party software CrossOver and installing the Windows version of OpenXcom.