openmw.org

I think that's a packaging issue, so we'll need a replacement RC11 rather than a whole new round of RCs.

AnyOldName3 wrote: ↑22 Jun 2023, 23:41 I think that's a packaging issue, so we'll need a replacement RC11 rather than a whole new round of RCs.

Ok. Same issue occurred for me with both RC9 and RC10, FYI, so it may be an issue with how they are being compiled in general(?). Thanks!

willlone wrote: ↑23 Jun 2023, 00:29

AnyOldName3 wrote: ↑22 Jun 2023, 23:41 I think that's a packaging issue, so we'll need a replacement RC11 rather than a whole new round of RCs.

Ok. Same issue occurred for me with both RC9 and RC10, FYI, so it may be an issue with how they are being compiled in general(?). Thanks!

Give this try?
https://mega.nz/file/zNs00RaT#fqoBJuKOE ... ndey1zvQWk

I did a completely clean build using the same settings as the M1, using the same package versions. I validated that it runs, at least on 13.4

I've put that link in the blog post and labelled it as RC11.1.

psi29a wrote: ↑23 Jun 2023, 10:12

willlone wrote: ↑23 Jun 2023, 00:29

AnyOldName3 wrote: ↑22 Jun 2023, 23:41 I think that's a packaging issue, so we'll need a replacement RC11 rather than a whole new round of RCs.

Ok. Same issue occurred for me with both RC9 and RC10, FYI, so it may be an issue with how they are being compiled in general(?). Thanks!

Give this try?
https://mega.nz/file/zNs00RaT#fqoBJuKOE ... ndey1zvQWk

I did a completely clean build using the same settings as the M1, using the same package versions. I validated that it runs, at least on 13.4

Just tried and I still get the launch failure here..

"Symbol not found: __ZNKSt3__115basic_stringbufIcNS_11char_traitsIcEENS_9allocatorIcEEE3strEv
Referenced from: /Applications/OpenMW.app/Contents/MacOS/../Frameworks/libyaml-cpp.0.7.dylib (which was built for Mac OS X 13.0)
Expected in: /usr/lib/libc++.1.dylib"

I am starting to wonder if it is an issue with my system, although that doesn't make sense -- I recently did a complete wipe / re-instal of Catalina on this MacBook, so it should all be in working order. I am happy to keep testing these builds to see if they will open if that is helpful.

Linux targz package RC11:

64 Bit

And that's a full suite of RCs on the blog.

The dump in that last file is for RC10, not RC11, but it looks like it's the same issue as in your previous dumps, except now we can actually analyse it as we can see what build you were using. We'd stopped investigating because you told us that RC8 fixed it.

I've made https://gitlab.com/OpenMW/openmw/-/issues/7442.

Can you please go there and answer the questions? Otherwise we've got no hope of figuring out what's going wrong.

Hey just wondering about what I can do to help fix the issue with the MacOS Intel builds.. I am happy to provide any information needed, with the caveat that you may need to explain to me how to find or do certain things.

I would personally be pretty bummed if OpenMW did not run on macOS Catalina, and also imagine I am not the only person running Morrowind on that specific system. Although it seems like I may be the only person testing the builds from there.

Could you try building it yourself?

https://wiki.openmw.org/index.php?title ... etup#macOS

Obviously I would lo figure things out what's going on. We need more people to test. ^^

So far it's just you and me.