I've confirmed that my 4.2.0 builds work fine on BigSur but
the 4.1.8 builds, even using Xcode10 and the 10.13SDK still
result in core on macOS11. Below you'll find the stack.
My initial thoughts are that it is NOT a build issue, but
rather a code one, so I'll start some investigation with that
mindset and especially look at the diffs between AOO418 and
AOO42X that might be key.
There are professional, non-trivial Native OSX apps that don't run on
Big Sur. For Instance Quark is one of them and it has no compatible
version currently (well, as of about a month ago). We had to create
another bootable partition to go back to Catalina so my wife could work.
She is a graphic artist doing page layout for a small local news paper.
She has had enough and is now moving to InDesign.
We also had problems when we moved to Catalina from several versions
back. Had to replace most of her professional software.
The problem may be incompatibilities in the third party software such as
boost, Java, and/or underlying OSX provided interfaces, etc. I don't
know if the build rebuilds all the the third party software. The
libraries such as boost (or AOO) may be using deprecated APIsand may not
be checkingreturn codes/exceptions appropriately in the libraries or in
AOO code. Another possibility, from what I've read in the past Apple has
let some deprecated APIs fail silently in the past. OSX has apparently
changed enough that they have moved the designation from OSX to OS11.
The problem may be deeper than just the AOO code.
Big Sur XCode 12 is the current version for OS11. Was AOO 4.2.0 built
with this? BTW, this version builds universal apps by default which
should make porting to OS11 and Apple Silicon much easier in the short term.
Another question just occurred to me. Are the versions of the Java JDK
the same for both builds and is the same JRE used at runtime?