Opened 5 years ago
Closed 4 years ago
#60267 closed defect (fixed)
mpv-0.31 fails to build on Catalina -- failed to import bridging header
Reported by: | Liontooth (David Liontooth) | Owned by: | Ionic (Mihai Moldovan) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | fracai, i0ntempest | |
Port: | mpv |
Description
$ sudo port install mpv ---> Computing dependencies for mpv ---> Fetching archive for mpv ---> Attempting to fetch mpv-0.31.0_0+audiocd+bundle+dvd+libarchive+network+opengl+osd+python27+rubberband.darwin_19.x86_64.tbz2 from https://packages.macports.org/mpv ---> Attempting to fetch mpv-0.31.0_0+audiocd+bundle+dvd+libarchive+network+opengl+osd+python27+rubberband.darwin_19.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/mpv ---> Attempting to fetch mpv-0.31.0_0+audiocd+bundle+dvd+libarchive+network+opengl+osd+python27+rubberband.darwin_19.x86_64.tbz2 from http://aus.us.packages.macports.org/macports/packages/mpv ---> Fetching distfiles for mpv ---> Verifying checksums for mpv ---> Extracting mpv ---> Configuring mpv ---> Building mpv Error: Failed to build mpv: command execution failed
:info:build <unknown>:0: error: failed to import bridging header '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_mpv/mpv/work/mpv-player-mpv-569a0a3/osdep/macOS_swift_bridge.h'
Attachments (1)
Change History (10)
Changed 5 years ago by Liontooth (David Liontooth)
comment:1 Changed 5 years ago by mf2k (Frank Schima)
Cc: | Ionic removed |
---|---|
Milestone: | MacPorts 2.7.0 |
Owner: | set to Ionic |
Status: | new → assigned |
comment:2 Changed 5 years ago by fracai
Cc: | fracai added |
---|
comment:3 Changed 5 years ago by i0ntempest
Cc: | i0ntempest added |
---|
comment:4 Changed 5 years ago by i0ntempest
comment:5 Changed 5 years ago by kencu (Ken)
modules are a new feature and we are seeing issues with them.
my guess is it might build if the SDK used was the original Xcode SDK.
comment:6 Changed 5 years ago by i0ntempest
Thanks, adding use_xcode yes
finally fixed the build. Should this be applied globally? If not the PR is ready for review.
comment:7 Changed 5 years ago by kencu (Ken)
Well -- anywhere that modules are enabled. It's probably an Xcode test, I guess, rather than an os.version test we will need -- I'm sorry, off the top of my head, I'm not 100% certain which Xcode started supporting modules. I think we just have to do some trial and error unless someone can find the tiny little page on the internet that tells us...
comment:8 Changed 5 years ago by i0ntempest
Okay, I'd say maybe apply the fix for Xcode 11+ and macOS 10.15+ for now and tweak the condition later if error occurs somewhere else.
comment:9 Changed 4 years ago by i0ntempest
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_mpv/mpv/main.log