https://bugs.winehq.org/show_bug.cgi?id=56218
--- Comment #6 from Gcenx gcenx83@gmail.com --- (In reply to mestesso.me from comment #4)
Not yet solved.
brew officially supports macOS Monterey and later (as of Jan 22nd 2024)
(In reply to mestesso.me from comment #4)
It is a Wine Bug! Homebrew only delivers what Wine puts in!
You didn’t read me message at all, I no longer own a functional Intel Mac so I can’t build for these legacy targets.
(In reply to mestesso.me from comment #4)
So.. The solution adopted by others is to keep old version available, like “wine-stable@8.21” or “wine-stable@9.0-rc5”, and not only latest “wine-stable”.
That’s possible, why not using that possibility?!? Packages are on github, so..
Again brew only officially supports macOS Monterey and greater, if brew wants to add a fallback for these legacy platforms that’s upto brew.
However even if they’re somehow convinced we’ll no longer take bug for these legacy versions of wine.
Again I personally can’t provide packages for legacy versions of macOS as I no longer own an Intel Mac that’s capable of running said legacy versions of macOS.
Unless someone wants to ether donate me a system that’s capable of running legacy version of macOS or wants to provide package for these legacy macOS versions there’s nothing I can do.
If you read my message again I do provide a macports overlay to assist in holding wine on macOS, upstream macports wine package maintainer hasn’t updated the packages in years and shows no interest nor desire to do so anymore. All my attempts to get fixes into macports for building +universal on macOS Mojave ware shot down and I’m not allowed to take over the wine ports.