[MacPorts] #63694: mpv: fatal error encountered while reading from module 'Foundation'

MacPorts noreply at macports.org
Tue Nov 9 17:00:03 UTC 2021


#63694: mpv: fatal error encountered while reading from module 'Foundation'
---------------------------+------------------------
  Reporter:  ShadSterling  |      Owner:  i0ntempest
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.7.1
Resolution:                |   Keywords:
      Port:  mpv           |
---------------------------+------------------------

Comment (by i0ntempest):

 Replying to [comment:25 Gandoon]:
 > Replying to [comment:24 i0ntempest]:
 > > For 10.15 use Xcode 11. If you don't know the version you need to
 build this, take a look at the buildbot log of your system version, here
 on the right: https://ports.macports.org/port/mpv/details/
 > Thank you for input, but it doesn't explain why this is the only port
 that refuses to build for me when all other builds just fine. The last
 working mpv
 (@0.33.1_1+audiocd+bluray+bundle+caca+dvd+jack+libarchive+network+opengl+osd+pulseaudio+python39+rubberband+screenshot+uchardet+x11)
 I have was built in April this year with this exact Xcode etc. I have been
 using Xcode 12 for the better part of a year now and 12.4 since soon after
 its release. I do not see any reason why this would be the point where I
 would need to ''downgrade'' a system that works in all other cases except
 for mpv.
 >
 > Do you know what might be the issue here though? Because nothing about
 the Apple originated build system has changed between the build of
 0.33.1_1 and now. Something in the updated port must be at fault here
 rather than a "too new" Xcode. I have tried to dig around myself, but not
 really been able to pinpoint the exact issue. I suspect something to do
 with waf (that I know almost nothing about at this point), but both seem
 to use wav v2.0.22, so I don't know.

 All I know is something weird could happen when you try building Swift
 code with mismatched Xcode and/or SDK. Xcode 12 has SDK for macOS 11 and
 not 10.15, although theoretically you can use new SDKs to target old
 systems, the changes could still break stuff, which is the case here.
 Unfortunately I'm not skilled enough to do Swift debugging and the
 original maintainer isn't really active. I'm thinking maybe I'm gonna shot
 an email into MP developer list for some help.
 >
 > Also, a small update… the outcome looks remarkably similar to this
 ticket: [https://trac.macports.org/ticket/60267] regarding someones
 failure to build a slightly earlier version (mpv-0.31.0_0, note the
 similarity of the log contents, especially at the end).\\
 > The main differences between that build and my build seems to be that
 Xcode 11.4 and Python 2.7 was used instead of Xcode 12.4 and Python 3.9 in
 my case, but a few other things were older as well of course, but as I
 said, I successfully built the previous version of mpv with the present
 system.

-- 
Ticket URL: <https://trac.macports.org/ticket/63694#comment:27>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list