May 2016 - macports-tickets - lists.macosforge.org

[MacPorts] #50966: Qt5 PortGroup files; preparing for port:qt5-kde and the KF5 port family
by MacPorts 14 Jun '16

14 Jun '16

#50966: Qt5 PortGroup files; preparing for port:qt5-kde and the KF5 port family -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: qt5, qt5-kde -------------------------+-------------------------------- I'm submitting my proposed changes to the Qt5 PortGroup inn another attempt to gain some attention for and traction on the subject of the KF5 port family which have a strong (*) dependency on a Qt5 version with dedicated patches. This family and the corresponding `port:qt5-kde` are currently in extended testing and ought to be committed in a hopefully not-too-far future. The changes are relatively straightforward and aim to maximise the extent to which users will be able to install either of the Qt5 ports as an alternative, much like this is currently possible with `-devel` ports. - A Qt5 KDE PortGroup (qt5-kde-1.0.tcl) is introduced that provides the configuration details for `port:qt5-kde`. It also defines and sets the variant `+qt5kde`. - The current qt5-1.0.tcl single-file PortGroup is renamed to qt5-mac-1.0.tcl (and can be renamed to anything else deemed more appropriate) - The Qt5 1.0 PortGroup (qt5-1.0.tcl) is replaced with a "header PortGroup", i.e. it includes one of the 2 PortGroup alternatives. The Qt5 KDE PortGroup is included if and only if 1) a port includes it explicitly; `PortGroup qt5-kde 1.0` (making it incompatible with a set-up where `port:qt5` is installed and active). 2) `port:qt5-kde` has been installed by the user. This is the only scenario in which a regular port will use qt5-kde "by default". 3) No Qt5 port has been installed when the user installs a Qt5-dependent that indicates a preference to qt5-kde, i.e.: {{{ set qt5.prefer_kde yes PortGroup qt5 1.0 }}} In all other cases, the current Qt5 PortGroup and `port:qt5` are used. The `+qt5kde` variant ensures that binary builds of Qt5-dependent port can be distinguished as a function of what Qt5 port they are built against. Ports built against `port:qt5` appear to work fine against `port:qt5-kde`, but the reverse is less likely to be true, esp. for KF5 ports that were built against `port:qt5-kde`. It would be possible to declare the `qt5kde` variant in the "header" PortGroup, and use it instead of or in addition to `qt5.prefer_kde`. I have no objection against that but think that it may give a bit too much control to users which either doesn't make much sense (telling a port to use "the other Qt5 port", = the one not installed) or is redundant or even counter productive. The Qt5 "header" PortGroup also introduces a procedure to facilitate declaring dependencies on specific Qt5 components, e.g. {{{ qt5.depends_component qtbase qtsvg qt3d }}} this expands to the appropriate subports dependencies (i.e. on `qt5-qtbase, qt5-qtsvg, qt5-qt3d` or `qt5-kde-qtbase, qt5-kde-qtsvg, qt5 -kde-qt3d`). The procedure has initial support for an optional table of dependency patterns that can be declared in the specific PortGroup (cf. `qt5_component_lib` in qt5-kde-1.0.tcl ; there is an expansion issue with the use of variables in the elements of that table that I haven't been able to figure out yet). Note that `port:qt5-kde` only provides a true subport for QtWebEngine; the remaining component subports are stubs that depend on `port:qt5-kde`. *) The KF5 dependency on `port:qt5-kde` is strong but obligatory only in the sense that using a "stock" Qt5 breaks a lot of functionality and would require significant patching that just doesn't make sense for something like MacPorts of almost all KF5 ports. -- Ticket URL: <https://trac.macports.org/ticket/50966> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #51341: ldas-tools@2.4.2_1 + build error: command execution failed
by MacPorts 13 Jun '16

13 Jun '16

#51341: ldas-tools(a)2.4.2_1 + build error: command execution failed ------------------------+-------------------------------- Reporter: yfwang42@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ldas-tools ------------------------+-------------------------------- I am trying to install LAL suite ( https://wiki.ligo.org/viewauth/DASWG/MacPorts) on OS X EI Captain (version: 10.11.4). However, I couldn't install the "ldas-tools" in this suite. I ran "sudo port clean ldas-tools" and "sudo port install ldas-tools". Then I received the following: {{{ ---> Computing dependencies for ldas-tools ---> Fetching archive for ldas-tools ---> Attempting to fetch ldas- tools-2.4.2_1+python27.darwin_15.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/ldas-tools ---> Attempting to fetch ldas- tools-2.4.2_1+python27.darwin_15.x86_64.tbz2 from http://nou.nc.packages.macports.org/pub/macports/packages.macports.org /ldas-tools ---> Attempting to fetch ldas- tools-2.4.2_1+python27.darwin_15.x86_64.tbz2 from https://packages.macports.org/ldas-tools ---> Fetching distfiles for ldas-tools ---> Verifying checksums for ldas-tools ---> Extracting ldas-tools ---> Applying patches to ldas-tools ---> Configuring ldas-tools ---> Building ldas-tools Error: org.macports.build for port ldas-tools returned: command execution failed Please see the log file for port ldas-tools for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_science_ldas-tools/ldas-tools/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ldas-tools failed }}} In the main.log, I found the following error: {{{ :info:build In file included from FrDetector3.cc:1: :info:build ./FrDetector.cc:272:1: error: all paths through this function will call itself [-Werror,-Winfinite -recursion] }}} By the way, my Xcode version is 7.3.1 -- Ticket URL: <https://trac.macports.org/ticket/51341> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #48973: org.macports.build for port ldas-tools returned: command execution failed
by MacPorts 13 Jun '16

13 Jun '16

#48973: org.macports.build for port ldas-tools returned: command execution failed -----------------------------+-------------------------------- Reporter: pilondon2@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: ldas-tools, lal | Port: ldas-tools -----------------------------+-------------------------------- I am attempting to install LAL (https://wiki.ligo.org/viewauth/DASWG/MacPorts) on OS X Yosemite. I have run "sudo port install lscsoft-deps" and recieved the following: {{{ ---> Fetching archive for ldas-tools ---> Attempting to fetch ldas-tools-2.4.0_0.darwin_14.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ldas-tools ---> Attempting to fetch ldas-tools-2.4.0_0.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/ldas-tools ---> Attempting to fetch ldas-tools-2.4.0_0.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/ldas-tools ---> Fetching distfiles for ldas-tools ---> Verifying checksums for ldas-tools ---> Extracting ldas-tools ---> Configuring ldas-tools ---> Building ldas-tools Error: org.macports.build for port ldas-tools returned: command execution failed Error: Failed to install ldas-tools }}} I have tried "port clean ldas-tools" to no avail. The relevant line of the main.log file appears to be "Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_science_ldas-tools/ldas-tools/work/ldas- tools-2.4.0" && /usr/bin/make -j4 -w all :error:build org.macports.build for port ldas-tools returned: command execution failed". The full log file has been attached. -- Ticket URL: <https://trac.macports.org/ticket/48973> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #51246: submission: port:zfs and port:zfs-devel
by MacPorts 12 Jun '16

12 Jun '16

#51246: submission: port:zfs and port:zfs-devel -------------------------+-------------------------------- Reporter: rjvbertin@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: -------------------------+-------------------------------- I've finally gotten around to making a port for the OS X implementation of the ZFS filesystem, now that it seems to have reached a sufficient maturity (read: it no longer causes system instability after having done a few simple tests). I don't think I have to introduce ZFS here, but for those who really don't know what it is: It's the filesystem that Apple once considered as an officially supported FS, if not the default for OS X. It provides very high data reliability (*), is extremely flexible & scalable and has a potential for very good performance (though not necessarily trivial and probably not yet in the OS X implementation). It also offers optional on- the-fly compression including using the lz4 scheme which is fast enough to improve I/O to slow media (time spent de/compressing is less than the increase in data transfer times). *) even when using a single partition because it can write each file in multiple copies - a feature that prevented me from losing no more than a single trivial file from my Linux rig when a disk started dropping sectors on me at a rate I never saw before a few days ago. I already tested an earlier release from an officialy installer on Bradley's (pixilla) VM about a year ago, using it to put a whole MacPorts install in a dataset mounted on /opt/local, with compression, case sensitivity and redundancy for important parts like the registry. The current implementation installs everything properly into ${prefix}, kernel extensions included. That works fine on OS X 10.9 (with a single warning when loading eacho of the kexts the 1st time). I'd be very interested in feedback from users on more recent versions of OS X, notably 10.11 . I suspect it might be necessary to put the kernel stuff into /Library when SIP is not disabled (?) Notes: - ZFS does tend to like having sufficient memory. On systems with <8Gb it might be wise to read up on reducing the max. amount used by ARC (not related to ObjC's ARC ;)) - This is a project that's seeing active development and continuous improvement. There's a `port:zfs` but I would strongly suggest to test `port:zfs-devel`. - In fact, I'd (almost) suggest to use an official installer from the project's website instead of using `port:zfs`, because that should give better system integration "out of the box". On the other hand, the MacPorts version should be less intrusive/invasive and easier to uninstall. WARNING: This port installs kernel extensions which get loaded automatically when using ZFS. As a result it should PROBABLY NOT be deactivated, uninstalled or reinstalled without taking the following precautions: 1) unmount (export) all ZFS datasets and pools 2) kextunload zfs.kext 3) kextunload spl.kext Question: is there a phase where one could check if either of the kexts is loaded, and raise an error if that is the case (pre-deactivate would be perfect)? -- Ticket URL: <https://trac.macports.org/ticket/51246> MacPorts <https://www.macports.org/> Ports system for OS X

1 11

[MacPorts] #50229: py-ngl: use compilers portgroup
by MacPorts 11 Jun '16

11 Jun '16

#50229: py-ngl: use compilers portgroup -------------------------+-------------------- Reporter: dstrubbe@… | Owner: petr@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: haspatch | Port: py-ngl -------------------------+-------------------- py-ngl should use the compilers portgroup instead of the obsolete recipe for Fortran variants, as in the attached patch. It can also be updated to version 1.4.0, and have automatic downloading enabled, as was done for py- nio and as discussed in ticket #42541. -- Ticket URL: <https://trac.macports.org/ticket/50229> MacPorts <https://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #50836: vpython @6.11 new Portfile
by MacPorts 10 Jun '16

10 Jun '16

#50836: vpython @6.11 new Portfile -------------------------+-------------------------------- Reporter: maugustin@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: vpython -------------------------+-------------------------------- New portfile for vpython (Visual Python, http://vpython.org) This port needs a patch in setup.py to take the mt version of boost_python and boost_signal. This port depends on ttfquery, that is submitted in ticket https://trac.macports.org/ticket/50809 -- Ticket URL: <https://trac.macports.org/ticket/50836> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #47197: cmake-based ports: add cmake.out_of_source yes/no
by MacPorts 09 Jun '16

09 Jun '16

#47197: cmake-based ports: add cmake.out_of_source yes/no -------------------------+------------------------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: Bear Cockatrice FreeRDP Io | LucenePlusPlus OpenGTL OpenSceneGraph | OpenSceneGraph-devel PlasmaClient PlasmaShop | TOra Vidalia airspy allegro allegro5 alps apbs | apiextractor armadillo assimp assimp2 autopano- | sift-c avidemux bladeRF blosc bob box2d bullet | ceres-solver cgal charm chemkit chipmunk choqok | chromaprint clhep clucene clucene-devel coinor- | liblemon collada-dom cuneiform cutecom-qt4-mac | dcmtk dolfin ebook-tools efte eigen eigen3 | emergent ettercap exiv2 falcon fann fcl flann | freealut freecad freecell-solver gate gccxml- | devel geant4 generatorrunner gerbil gl2ps glfw | gmsh gmt5 gnudatalanguage gnuradio gr-air-modes | gr-ais gr-baz gr-dvbs gr-dvbs2 gr-dvbt gr- | fcdproplus gr-fosphor gr-iqbalance gr-mac gr- | osmosdr gr-rds graphite2 h3dutil hackrf | htcondor hugin-app iAIDA indi indi_maxdomeii | json_spirit kealib kst lensfun lib2geom libLASi | libbiosig libccd libdynd libftdi libgit2 | libhsplasma liblas liblastfm libmsn | libmusicbrainz3 libnifalcon libpcl | libphonenumber-cpp libplist libproxy libssh | libtuxcap lmms lua-luabitop magicspp mariadb | mariadb-10.0 mariadb-10.1 metis mysql55 mysql55 | -connector-cpp mysql56 newmat nifticlib nomacs | oce ogre ompl openal-soft openbabel opencv | openjpeg orfeotoolbox orocos-kdl orocos-rtt | osgswig-devel oxygen-icons parmetis pdf2htmlex | pdfpc percona pgrouting phonon phonon-backend- | gstreamer physfs piklab playerstage-player | playerstage-stage podofo polkit-qt portmidi pqp | py-dynd py-pyside py-pyside-tools py-shiboken | qfsm qgis qhull qlandkartegt qlandkartegt- | garmindev qlipper qore-qt4-module quassel | rabbitmq-c root6 rsgislib rspamd rtl-sdr | scalapack scantailor scribus sdcv seqan-apps | sfcgal shogun-devel sigil soci streamlog | synergy synergy-devel sysdig tagainijisho | taglib task telepathy-qt tigervnc tinyxml | toluapp uhd usbmuxd viennacl vigra vramsteg | vrpn vtk vtk5 vxl wbxml2 weechat wesnoth | widelands wxLua xrootd yajl yaml-cpp zorba -------------------------+------------------------------------------------- Following #33259 and r134128 it would be nice if maintainers of ports using the cmake PortGroup would add the following line to their ports {{{ cmake.out_of_source yes }}} and test whether the ports still compile fine (no need for a revbump). Some ports already use out-of-source builds, so those ports would need a minor clean-up. If the port doesn't work that way, please add an explicit {{{ cmake.out_of_source no }}} with a short comment (and possibly file an upstream bug report). Once all the ports are tested, this would become the default behaviour and the line (setting `yes`) will be removed from the ports. -- Ticket URL: <https://trac.macports.org/ticket/47197> MacPorts <https://www.macports.org/> Ports system for OS X

1 54

[MacPorts] #51233: Codeblocks installation fails on El Capitan 10.11.4
by MacPorts 09 Jun '16

09 Jun '16

#51233: Codeblocks installation fails on El Capitan 10.11.4 ---------------------------------+-------------------------------- Reporter: luc.bouge@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: Failure, El Capitan | Port: Codeblocks ---------------------------------+-------------------------------- My Mac has been reformatted to El Capitan 10.11.4 a few weeks ago. The whole disk has been erased and everything has been reinstalled: Xcode, MacPorts, all the ports. I did not modify the configuration files in directory /opt/local/etc/macports/, and everything went fine, except for codeblocks. As far as I can see, there is a compatibility problem with wxWidgets 3.0. I include the log. Luc. -- Ticket URL: <https://trac.macports.org/ticket/51233> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #51520: llvm-3.9 @3.9-r270400_0+assertions+debug build failure on snow leopard due to missing strnlen function - and fix
by MacPorts 09 Jun '16

09 Jun '16

#51520: llvm-3.9 @3.9-r270400_0+assertions+debug build failure on snow leopard due to missing strnlen function - and fix ------------------------------------+-------------------------------- Reporter: kenneth.f.cunningham@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: snowleopard | Port: llvm-3.9 ------------------------------------+-------------------------------- Sorry I haven't figured out the diff files just yet. llvm-3.9 build fails at 12% and then at 98% with error strnlen function not found to fix: in this file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.9/llvm-3.9/work/trunk/lib/ObjectYAML/MachOYAML.cpp and in this file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.9/llvm-3.9/work/trunk/tools/obj2yaml/macho2yaml.cpp add this replacement function after <string.h> and build succeeds (found an example in the cctools patches): static size_t strnlen(const char *s, size_t maxlen) { size_t len; for (len = 0; len < maxlen; len++, s++) { if (!*s) break; } return (len); } -- Ticket URL: <https://trac.macports.org/ticket/51520> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

[MacPorts] #51221: py-bob-io-video: build fails with ffmpeg-3.0+
by MacPorts 09 Jun '16

09 Jun '16

#51221: py-bob-io-video: build fails with ffmpeg-3.0+ ----------------------+----------------------------- Reporter: devans@… | Owner: tiago.pereira@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: py-bob-io-video ----------------------+----------------------------- As noted in #50694, the current version of py{27,34}-bob-io-video fails to build with ffmpeg 3.0+ due to the use of deprecated API removed in ffmpeg 3.0. {{{ [ 25%] Building CXX object CMakeFiles/bob_io_video.dir/opt/local/var/macports/build /_opt_macports_trunk_dports_python_py-bob-io-video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp.o /Applications/Xcode-7.2/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -DBLITZ_VERSION=\"0.10\" -DHAVE_AVFORMAT_ALLOC_OUTPUT_CONTEXT2=None -DHAVE_BLITZ=1 -DHAVE_LIBAVCODEC=1 -DHAVE_LIBAVFORMAT=1 -DHAVE_LIBAVUTIL=1 -DHAVE_LIBSWSCALE=1 -DLIBAVCODEC_VERSION=\"57.24.102\" -DLIBAVFORMAT_VERSION=\"57.25.100\" -DLIBAVUTIL_VERSION=\"55.17.103\" -DLIBSWSCALE_VERSION=\"4.0.100\" -DNO_IMPORT_ARRAY=1 -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -DPY_ARRAY_UNIQUE_SYMBOL=BOB_NUMPY_C_API -D__STDC_CONSTANT_MACROS=None -Dbob_io_video_EXPORTS -I/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/bob/io/base/include -isystem /opt/local/include -I/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/bob/core/include -I/opt/local/var/macports/build /_opt_macports_trunk_dports_python_py-bob-io-video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/include -I/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/bob/blitz/include -isystem /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/numpy/core/include -std=c++0x -pedantic -Wall -pthread -Qunused-arguments -m64 -arch x86_64 -isysroot /Applications/Xcode-7.2/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -mmacosx-version-min=10.10 -fPIC -o CMakeFiles/bob_io_video.dir/opt/local/var/macports/build /_opt_macports_trunk_dports_python_py-bob-io-video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp.o -c /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io-video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp In file included from /opt/local/var/macports/build /_opt_macports_trunk_dports_python_py-bob-io-video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:28: /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/include/bob.io.video/utils.h:125:7: error: unknown type name 'PixelFormat'; did you mean 'AVPixelFormat'? PixelFormat source_pixel_format, PixelFormat dest_pixel_format); ^~~~~~~~~~~ AVPixelFormat /opt/local/include/libavutil/pixfmt.h:61:6: note: 'AVPixelFormat' declared here enum AVPixelFormat { ^ In file included from /opt/local/var/macports/build /_opt_macports_trunk_dports_python_py-bob-io-video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:28: /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/include/bob.io.video/utils.h:125:40: error: unknown type name 'PixelFormat'; did you mean 'AVPixelFormat'? PixelFormat source_pixel_format, PixelFormat dest_pixel_format); ^~~~~~~~~~~ AVPixelFormat /opt/local/include/libavutil/pixfmt.h:61:6: note: 'AVPixelFormat' declared here enum AVPixelFormat { ^ In file included from /opt/local/var/macports/build /_opt_macports_trunk_dports_python_py-bob-io-video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:28: /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/include/bob.io.video/utils.h:138:49: error: unknown type name 'PixelFormat'; did you mean 'AVPixelFormat'? boost::shared_ptr<AVCodecContext> stream, PixelFormat pixfmt); ^~~~~~~~~~~ AVPixelFormat /opt/local/include/libavutil/pixfmt.h:61:6: note: 'AVPixelFormat' declared here enum AVPixelFormat { ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:716:34: error: use of undeclared identifier 'PIX_FMT_YUV420P'; did you mean 'AV_PIX_FMT_YUV420P'? retval->codec->pix_fmt = AV_PIX_FMT_YUV420P; ^~~~~~~~~~~~~~~~~~ AV_PIX_FMT_YUV420P /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:45:28: note: expanded from macro 'AV_PIX_FMT_YUV420P' #define AV_PIX_FMT_YUV420P PIX_FMT_YUV420P ^ /opt/local/include/libavutil/pixfmt.h:63:5: note: 'AV_PIX_FMT_YUV420P' declared here AV_PIX_FMT_YUV420P, ///< planar YUV 4:2:0, 12bpp, (1 Cr & Cb sample per 2x2 Y samples) ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:757:46: error: unknown type name 'PixelFormat'; did you mean 'AVPixelFormat'? boost::shared_ptr<AVCodecContext> codec, PixelFormat pixfmt) { ^~~~~~~~~~~ AVPixelFormat /opt/local/include/libavutil/pixfmt.h:61:6: note: 'AVPixelFormat' declared here enum AVPixelFormat { ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:814:12: warning: 'avpicture_alloc' is deprecated [-Wdeprecated-declarations] int ok = avpicture_alloc(&picture, pixfmt, codec->width, codec->height); ^ /opt/local/include/libavcodec/avcodec.h:4871:5: note: 'avpicture_alloc' has been explicitly marked deprecated here int avpicture_alloc(AVPicture *picture, enum AVPixelFormat pix_fmt, int width, int height); ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:862:2: error: unknown type name 'PixelFormat'; did you mean 'AVPixelFormat'? PixelFormat source_pixel_format, PixelFormat dest_pixel_format) { ^~~~~~~~~~~ AVPixelFormat /opt/local/include/libavutil/pixfmt.h:61:6: note: 'AVPixelFormat' declared here enum AVPixelFormat { ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:862:35: error: unknown type name 'PixelFormat'; did you mean 'AVPixelFormat'? PixelFormat source_pixel_format, PixelFormat dest_pixel_format) { ^~~~~~~~~~~ AVPixelFormat /opt/local/include/libavutil/pixfmt.h:61:6: note: 'AVPixelFormat' declared here enum AVPixelFormat { ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:1112:27: warning: 'av_free_packet' is deprecated [-Wdeprecated-declarations] if (p->size || p->data) av_free_packet(p); ^ /opt/local/include/libavcodec/avcodec.h:4040:6: note: 'av_free_packet' has been explicitly marked deprecated here void av_free_packet(AVPacket *pkt); ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:1149:26: warning: 'coded_frame' is deprecated [-Wdeprecated-declarations] if (stream->codec->coded_frame->key_frame) pkt->flags |= AV_PKT_FLAG_KEY; ^ /opt/local/include/libavcodec/avcodec.h:2945:35: note: 'coded_frame' has been explicitly marked deprecated here attribute_deprecated AVFrame *coded_frame; ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:1272:26: warning: 'coded_frame' is deprecated [-Wdeprecated-declarations] if (stream->codec->coded_frame && stream->codec->coded_frame->key_frame) ^ /opt/local/include/libavcodec/avcodec.h:2945:35: note: 'coded_frame' has been explicitly marked deprecated here attribute_deprecated AVFrame *coded_frame; ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:1272:56: warning: 'coded_frame' is deprecated [-Wdeprecated-declarations] if (stream->codec->coded_frame && stream->codec->coded_frame->key_frame) ^ /opt/local/include/libavcodec/avcodec.h:2945:35: note: 'coded_frame' has been explicitly marked deprecated here attribute_deprecated AVFrame *coded_frame; ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:1425:5: warning: 'av_free_packet' is deprecated [-Wdeprecated-declarations] av_free_packet(pkt.get()); ^ /opt/local/include/libavcodec/avcodec.h:4040:6: note: 'av_free_packet' has been explicitly marked deprecated here void av_free_packet(AVPacket *pkt); ^ /opt/local/var/macports/build/_opt_macports_trunk_dports_python_py-bob-io- video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp:1519:5: warning: 'av_free_packet' is deprecated [-Wdeprecated-declarations] av_free_packet(pkt.get()); ^ /opt/local/include/libavcodec/avcodec.h:4040:6: note: 'av_free_packet' has been explicitly marked deprecated here void av_free_packet(AVPacket *pkt); ^ 7 warnings and 7 errors generated. make[2]: *** [CMakeFiles/bob_io_video.dir/opt/local/var/macports/build /_opt_macports_trunk_dports_python_py-bob-io-video/py27-bob-io- video/work/bob.io.video-2.0.5/bob/io/video/cpp/utils.cpp.o] Error 1 make[1]: *** [CMakeFiles/bob_io_video.dir/all] Error 2 }}} Similar errors occur in bob/io/video/cpp/reader.cpp and bob/io/video/cpp/writer.cpp. Attached is a proposed patch that fixes the ffmpeg 3.0 build errors without effecting builds on earlier versions. Tested with ffmpeg 2.8.6 and 3.0.1. Let me know if you agree this patch can be committed. I'd like to do this as soon as possible so that we can upgrade ffmpeg to the 3.0 version series now at ffmpeg 3.0.1. Thanks -- Ticket URL: <https://trac.macports.org/ticket/51221> MacPorts <https://www.macports.org/> Ports system for OS X

1 4