They did. See https://forums.developer.apple.com/thread/121887 https://github.com/jedisct1/libsodium/issues/848 https://bitbucket.org/multicoreware/x265/issues/514/wrong-code-generated-on-macos-1015 https://github.com/Homebrew/homebrew-core/issues/45602 Evidently Apple turns -fstack-check on by default on mac os 10.15, which exposed this bug. One workaround is to add -fno-stack-check when compiling anything on Mac OS 10.15. Hopefully it'll be fixed in xcode 11.2.
On Sat, Oct 19, 2019 at 9:48 PM Dan Kegel <d...@kegel.com> wrote: > > Verified that the problem happens even with xcode 11.1. Filed a bug > with the brew folks, > https://github.com/Homebrew/homebrew-core/issues/45602 > in case they have any bright ideas.
