For me, the issue is whether it is, indeed, a code problem in 4.1.8 that requires fixes and thus a 4.1.9 release, or whether it is a *build* problem, that implies that building 4.1.8 with a newer SDK will resolve the problem. AFAICT, that question is still unresolved. What we DO know is that 4.2.0-dev works fine under Big Sur.
With that in mind, over the next week I may try building 4.1.8 but with various versions of Xcode and macOS SDKs... > On Dec 26, 2020, at 10:05 AM, Matthias Seidel <matthias.sei...@hamburg.de> > wrote: > > Hi Jim, > > Am 26.12.20 um 15:17 schrieb Jim Jagielski: >> It is more than likely that we may need to release a 4.1.9 just to >> accommodate BigSur. However, AOO >> is hardly unique in being an app that no longer works when someone upgrades >> to BigSur. The macOS >> community is replete w/ such apps. I'm not using that as an excuse, but that >> is what it is. > > More than once Apple did break something with an OS upgrade and fixed it > with one of the next updates... > > Let's see how macOS 11.2 (beta) behaves [1]. > > Regards, > > Matthias > > [1] > https://www.macrumors.com/2020/12/17/apple-seeds-macos-big-sur-11-2-public-beta-1/ > >> >> >>> On Dec 25, 2020, at 5:02 AM, Jörg Schmidt <joe...@j-m-schmidt.de> wrote: >>> >>> Hello, >>> >>> I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it >>> was also diligently discussed there. >>> But there seems to be no solution yet and at the same time the requests >>> from users who are practically not able to work anymore because AOO does >>> not work under BigSur continue. >>> >>> 1. >>> Is there any solution in sight? >>> >>> 2. >>> If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 >>> (BigSur) is currently not supported? >>> (This would give users the chance to wait with the update of MacOS to >>> version 11.0). >>> >>> >>> Sorry, my point of view is only that of a supporter who supports users day >>> by day (voluntarily in the community and professionally), I can't assess >>> the technical problems, but unfortunately I see that the current situation >>> is damaging our reputation. >>> >>> >>> >>> greetings, >>> Jörg >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
