Re: mpv, ffmpeg seg fault in macOS catalina

Thanks. I’ve used the migration process many times in the past, so no worries. I appreciate your taking the time to reply. > On Oct 19, 2019, at 10:08, Chris Jones wrote: > >> If I upgrade to Catalina (I already have Xcode 11.1) and install MacPorts >> for Catalina will ffmpeg stop working? >

Re: mpv, ffmpeg seg fault in macOS catalina

I’m sorry, but I don’t understand most of what was written in this thread, but I do have a simple question: If I upgrade to Catalina (I already have Xcode 11.1) and install MacPorts for Catalina will ffmpeg stop working? > On Oct 18, 2019, at 19:00, Gill Bates > wrote:

Re: mpv, ffmpeg seg fault in macOS catalina

Thanks all for the explanations and workaround. From: "Mojca Miklavec" To: "smogus" Cc: "macports-users" Sent: Friday, October 18, 2019 5:02:55 AM Subject: Re: mpv, ffmpeg seg fault in macOS catalina V čet., 17. okt. 2019 22:58 je oseba Gill Bates &l

Re: mpv, ffmpeg seg fault in macOS catalina

Hi, Workaround is to either blacklist the compiler which has this option turned on by default (which is what Chris replied) or in fact use a flag to disable this. But disabling this flag is not needed for non-broken compilers, so it's probably better to just blacklist the compiler, and the

Re: mpv, ffmpeg seg fault in macOS catalina

V čet., 17. okt. 2019 22:58 je oseba Gill Bates napisala: > 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

Re: mpv, ffmpeg seg fault in macOS catalina

Hi, 10.15 issues are worked around in https://github.com/macports/macports-ports/commit/36c3a9a2844ab979be1388280922b25d1f7b56ce

mpv, ffmpeg seg fault in macOS catalina

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: [