[MacPorts] #65098: avidemux @2.7.6_2 +aac+debug+dts+gettext+jack+lame+opus+sqlite+twolame+vorbis+vpx+x264+x265+xvid upgrade fails with error: expected unqualified-id

MacPorts noreply at macports.org
Thu Nov 17 01:17:39 UTC 2022


#65098: avidemux @2.7.6_2
+aac+debug+dts+gettext+jack+lame+opus+sqlite+twolame+vorbis+vpx+x264+x265+xvid
upgrade fails with error: expected unqualified-id
--------------------------+--------------------
  Reporter:  cooljeanius  |      Owner:  (none)
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.7.2
Resolution:               |   Keywords:
      Port:  avidemux     |
--------------------------+--------------------
Changes (by ryandesign):

 * cc: worldleather, macportsraf, mkuron (added)


Comment:

 Has duplicates #66275, #62136.

 Replying to [comment:2 kencu]:
 > in compilers that default to a newer c++ std, on case-insensitive file
 systems, the build is pulling in a file called VERSION in the source tree
 instead of the cxx header <version>.

 As far as I know it's not even about compilers that ''default to'' a newer
 C++ standard; it's about compilers that just ''support'' a newer C++
 standard, specifically C++20. Compilers that support C++20 implement its
 <version> header, and other headers include it, even when you are building
 with an earlier C++ standard.

 > usual trick is to delete or rename the VERSION file in the source tree
 to VERSION.txt for example, in a post-extract block.

 While renaming the VERSION file is one option, the failure is really
 because the directory that contains the VERSION file was specified as an
 include path (i.e. with the `-I` flag). Ideally the project should stop
 including that directory. If that directory contains files that need to be
 included (such as a config.h file), it may be preferable to change the
 build system so that the config.h file is located in a different
 directory.

 The failure is in the bundled copy of ffmpeg. The problem might already be
 solved by updating avidemux to a newer version (avidemux 2.8.1 is
 available; their release notes say the bundled ffmpeg was updated to 4.4.1
 in avidemux 2.8.0 and to 4.4.2 in avidemux 2.8.1), or the ffmpeg
 developers may already have fixed it and their fix can be backported to
 the bundled avidemux version, or avidemux can be fixed to use MacPorts
 ffmpeg instead of a bundled version.

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


More information about the macports-tickets mailing list