Print

[fri0701]

Hi there,
I'm trying to build LisaEm (from https://github.com/arcanebyte/lisaem/releases/tag/RC5-2025.03.15), and I'm running into several problems. I'm hoping someone here can point me in the right direction!

I cannot get the wxWidgets install script, as included with LisaEm, to finish successfully. At first I had to enforce the use of `clang` over `gcc`, but eventually after seeing heaps of errors and warnings, I decided to simply install the same version via homebrew and add it to my path. This seems to make LisaEm's build and install script happy enough to install the application into my Applications folder.

When I launch LisaEm, I get a window with the following information:
A debugging check in this application has failed.
./src/common/dpycmn.cpp(114): assert ""window"" failed in GetFromWindow(): invalid window

[01] wxDisplay::GetFromWindow(wxWindow const*)
[02] wxDisplay::wxDisplay(wxWindow const*)
[03] 0x0000000104103358
[04] wxEntry(int, wchar_t**)
[05] 0x0000000104106994

With a known good H ROM, if I power on the virtual Lisa, the application becomes unresponsive.

What steps should I try next? (I'm on an M1 MacBook Pro running Sequoia 15.3).

Thanks in advance! (I'm very glad someone has taken up Ray's reins on this project - it's very cool to see it continue on)

(would it perhaps be useful to make a section on this forum for LisaEm-specific issues or comments?)

[jamesdenton]

I can't help with this particular issue at the moment, but don't recall any glaring issues building on an M1 Pro with 15.3.x just a couple of weeks ago. I can guarantee there are issues with 15.4 at the moment that I am trying to work through. More wxWidgets than LisaEm at this point.

I will try and build a clean VM in UTM with 15.3 to see if I can recreate what you're seeing.

I also wonder how difficult it would be to just provide a known-working binary/application. IIRC this was possible at one time.

P.S. I think a subforum for LisaEm would be a good idea.

[fri0701]

I will try and build a clean VM in UTM with 15.3 to see if I can recreate what you're seeing.

Thank you! I'm happy to send more debugging info upon request in private messages if you think it'd be helpful (I didn't want to clutter the forum with heaps of wxWidgets logs).

[jamesdenton]

I will try and build a clean VM in UTM with 15.3 to see if I can recreate what you're seeing.

Thank you! I'm happy to send more debugging info upon request in private messages if you think it'd be helpful (I didn't want to clutter the forum with heaps of wxWidgets logs).

Feel free to post the logs to https://gisty.link; that's a pastebin-like site a friend of mine stood up recently to demonstrate some object storage capabilities. Nothing sensitive, of course.

Can you confirm you're not on 15.4? If 15.3, which subversion?

Anything in the logs about fp.h?

[fri0701]

Yes, Sequoia 15.3 (24D60)

Here's my complete wxWidgets build output:
https://gisty.link/7327834a426ea0daf21cbde9884d2225a7702c09

Looks like fp.h is mentioned.

[jamesdenton]

Yes, Sequoia 15.3 (24D60)

Here's my complete wxWidgets build output:
https://gisty.link/7327834a426ea0daf21cbde9884d2225a7702c09

Looks like fp.h is mentioned.

Created an issue for this:

https://github.com/arcanebyte/lisaem/issues/19

tl;dr: recent xcode changes brought in some changes to clang that had been implemented upstream a while back but are just making their way to macOS now. Looks like Chromium hit this earlier.

https://chromium-review.googlesource.com/c/chromium/src/+/5237620/2/third_party/libpng/pngpriv.h

I created a patch locally for wxWidgets, which can probably be implemented upstream for them as well. I also modified the configure command to use system zlib and not the (older) zlib provided by wxWidgets. This seems to have addressed the issues.

The latest master branch also includes some AWESOME patches by @TorZidan that helped address some issues with the profile code. You'll have to check those out.

Let me know if/how this recent patch works for you.

[fri0701]

Let me know if/how this recent patch works for you.

I can confirm that the latest changes fix the problem - thanks for looking into this so quickly! I look forward to experimenting with it in the coming days.