> On May 17, 2021, at 9:32 AM, Robert Helling via subsurface 
> <[email protected]> wrote:
> 
> Hi,
>> 
>> I was able to build fine on OS X before I upgraded to Big Sur - when running 
>> the build scripts now it fails very quickly with two errors: 
>> 
> 
> last weekend, I finally got around to update my Mac to Big Sur as well. By 
> now, I can successfully build here as well but I remember, in the process I 
> also saw a complaint about -lSystem but I cannot remember how that went away. 
> Reinstalling Xcode command line tools and throwing away the old build 
> directory were definitely required at some point.
> 
> But what kept took me the longest was understanding why my builds with debug 
> symbols and without optimisation (so the debugger is usable) failed with 
> realy strange error messages: Realising that the compiler flag for this is 
> not ā€ž-Gā€œ but in fact ā€ž-gā€œ (and that -G requires another argument so the next 
> bit on the command line get eaten up).

Oh, yes, definitely. Blow away your build directory, your install-root 
directory and any other build artifact that you have.
You have to restart with a fresh build. Big Sur breaks a lot of things (and is 
IMHO the worst macOS release since OS 9 - I haven't upgraded a single system to 
it with the exception of that one build VM... BigSur breaks so many things, so 
many devices, including trivial stuff like wired ethernet adapters, HDMI 
adapters, tons of software... and depending on how things go, in the "upgrade" 
you sometimes end up with a complete second set of all apps in some random 
directory, including a second system preferences app, which prevents system 
preferences from working with inanely stupid non-sensical error messages... 
what a mess)

/D

_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to