Hi, 10.15 issues are worked around in
https://github.com/macports/macports-ports/commit/36c3a9a2844ab979be1388280922b25d1f7b56ce <https://github.com/macports/macports-ports/commit/36c3a9a2844ab979be1388280922b25d1f7b56ce> https://github.com/macports/macports-ports/commit/2de6959b098cb95883863a2cf46575dfcf4c211c <https://github.com/macports/macports-ports/commit/2de6959b098cb95883863a2cf46575dfcf4c211c> They blacklist Xcode 11 clang, and thus the builds fallback to one of MacPorts MP’s clang compilers (9.0). Running Xcode 10 on macOS10.15 is unnecessary, and not really a good idea. For ‘Part B’ difficult to say as long as Xcode has issues (which I understand as off 11.1 it does). Until those are addressed hard to say if the project themselves also have issues to address. Chris > On 17 Oct 2019, at 9:58 pm, Gill Bates <[email protected]> wrote: > > I recently updated to catalina (10.15) and Xcode (11.1), installed MacPorts > from source (2.6.1) and had it build mpv and its dependencies. However, mpv > (and ffmpeg for example) do not run apparently related to some new default > compiler option enforcing 16 byte stack alignment? See: > https://trac.ffmpeg.org/ticket/8073 <https://trac.ffmpeg.org/ticket/8073> > https://github.com/mpv-player/mpv/issues/7053 > <https://github.com/mpv-player/mpv/issues/7053> > https://forums.developer.apple.com/thread/121887 > <https://forums.developer.apple.com/thread/121887> > > The advice seems to be to revert Xcode but will rebuilding everything with > Xcode 10.3 on macos 10.15 really be a workaround? Or is a better choice to > modify portfiles to include the CFLAG option to disable stack checks as > mentioned in the linked posts and use Xcode 11.1? > > "Part B" is a question for my understanding, is this a really an > Xcode/compiler issue or a problem with the source software packages? > > Thanks in advance for any advice.
smime.p7s
Description: S/MIME cryptographic signature
