#63753 closed defect (duplicate)
mpv @0.33.1: C11 atomics are required; you may need a newer compiler
Reported by: | mrkapqa | Owned by: | Ionic (Mihai Moldovan) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | mavericks | Cc: | i0ntempest |
Port: | mpv |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
---> Configuring mpv Warning: reinplace s/@@BACKEND@@/cocoa/ didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_mpv/mpv/work/mpv-0.33.1/TOOLS/config-maintainer Error: Failed to configure mpv: configure failure: command execution failed
Attachments (2)
Change History (5)
Changed 3 years ago by mrkapqa
comment:1 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | i0ntempest added |
---|---|
Description: | modified (diff) |
Keywords: | mpv removed |
Owner: | set to Ionic |
Status: | new → assigned |
Summary: | (10.9 , mpv) Error: Failed to configure mpv → mpv @0.33.1: C11 atomics are required; you may need a newer compiler |
comment:2 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → duplicate |
---|---|
Status: | assigned → closed |
Duplicate of your earlier bug report #62854.
comment:3 Changed 3 years ago by mrkapqa
thank you, it seems still an error
---> Attempting to fetch mpv-0.34.0.tar.gz from http://distfiles.macports.org/mpv ---> Verifying checksums for mpv ---> Extracting mpv ---> Configuring mpv Warning: reinplace s/@@BACKEND@@/cocoa/ didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_mpv/mpv/work/mpv-0.34.0/TOOLS/config-maintainer Error: Failed to configure mpv: configure failure: command execution failed
Changed 3 years ago by mrkapqa
Note: See
TracTickets for help on using
tickets.
The log says the error is:
The port already specifies:
You'd think that would have been enough...
The port was updated to 0.34.0 today; try again after running
sudo port selfupdate
. Let us know if that changes the error.