libVLC @2.2.8 +quartz fails to build against x264 @20180807

[TheLastLovemark]

Hi, as mentioned in ​ticket #58072 I recently completed a selfupdate after not doing so for a long while. When I tried to run port upgrade outdated and/or port rev-upgrade, something failed and I was presented with a list of broken ports, e.g.:

--->  Found 42 broken files, matching files to ports
rb-eventmachine is using libstdc++ (this installation is configured to use libc++)
sqlmap is using libstdc++ (this installation is configured to use libc++)
openmpi-gcc5 is using libstdc++ (this installation is configured to use libc++)
openmpi-gcc6 is using libstdc++ (this installation is configured to use libc++)
openmpi-gcc49 is using libstdc++ (this installation is configured to use libc++)
--->  Found 11 broken ports, determining rebuild order
DEBUG: Broken: R-app
DEBUG: Broken: enblend
DEBUG: Broken: ntop
DEBUG: Broken: objectmarker
DEBUG: Broken: libkdcraw
DEBUG: Broken: libVLC
DEBUG: Broken: rb-eventmachine
DEBUG: Broken: sqlmap
DEBUG: Broken: openmpi-gcc5
DEBUG: Broken: openmpi-gcc6
DEBUG: Broken: openmpi-gcc49
DEBUG: Processing port R-app @0:1.68_1  
DEBUG: Processing port enblend @0:4.1.5_4  
DEBUG: Processing port hugin-app @0:2018.0.0_3 +accelerate+python27 
DEBUG: Processing port luminance-hdr @0:2.5.1_4 +external 
DEBUG: Processing port ntop @0:5.0.1_3  
DEBUG: Processing port objectmarker @0:20070501_2  
DEBUG: Processing port libkdcraw @0:4.14.3_5  
DEBUG: Processing port libVLC @0:2.2.8_7 +quartz 
DEBUG: Processing port rb-eventmachine @0:0.12.10_0  
DEBUG: Processing port rb-twitter-stream @0:0.1.14_0  
DEBUG: Processing port rb-tweetstream @0:1.0.4_0  
DEBUG: Processing port sqlmap @0:0.9_1 +python27 
DEBUG: Processing port openmpi-gcc5 @0:3.0.0_0 +fortran 
DEBUG: Processing port openmpi-gcc6 @0:3.0.0_0 +fortran 
DEBUG: Processing port openmpi-gcc49 @0:3.0.0_0 +fortran 
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt:
 R-app @1.68
 enblend @4.1.5
 ntop @5.0.1
 objectmarker @20070501
 libkdcraw @4.14.3
 libVLC @2.2.8+quartz
 rb-eventmachine @0.12.10
 sqlmap @0.9+python27
 openmpi-gcc5 @3.0.0+fortran
 openmpi-gcc6 @3.0.0+fortran
 openmpi-gcc49 @3.0.0+fortran
Continue? [Y/n]:

Initially, the list was much longer and I was able to manually upgrade some of the ports (not shown). The first one I came here for help with is the ticket mentioned above (​#58072). I was redirected to try the solution suggested at ​ticket #58066 by kencu, which worked. I tried a similar solution with libVLC using variants, for example: port -vvvvv -d install libvlc +full +x11. This did not work.

Am I going to have to submit a ticket for every port in the above list?

The main.log file for libVLC is attached.

I have already tried manually upgrading all of the above ports with no success. Any help you can offer is greatly appreciated.

[TheLastLovemark]

libVLC +full +x11 main.log file

[kencu (Ken)]

It looks like libvlc will need a patch for the upgrade in libx264 similar to the one for mplayer; maybe even the same patch would work.

[TheLastLovemark]

Is there any immediate action to take on my part? Or should I wait for the wizards to work their magic?

Thanks for the timely response on a Saturday.

[jmroot (Joshua Root)]

As Ken mentioned there is a build fix needed for libvlc here. But there is also the side issue that rev-upgrade does seem to be passing variants down to dependencies when it shouldn't (problematic when there are potentially conflicting variants). See ML thread starting here: ​https://lists.macports.org/pipermail/macports-users/2019-January/046303.html

Not sure if anyone cared enough to file a ticket for that yet.

[RJVB (René Bertin)]

I know I should give my VLC port some love but I keep not getting around to it (real love/hate relationship with that port and the frequent updates to dependencies that break it!)

Nobody interested in a co-maintainership to come up with a VLC 3+ based "current" port that will hopefully require less work, and a VLC2@2.2.8 (or so) port for 10.9 and earlier ... which would still get broken way too often? I do have a "VLC-test" port in my macstrop repo that currently has a pending PR for an upgrade to 3.0.6 .

[TheLastLovemark]

OK, I've read the thread at ​https://lists.macports.org/pipermail/macports-users/2019-January/046303.html.

I do have multiple versions of python installed (python27, python34, and python35), though none of them appear to be variants releated libVLC (afaik).

I'll try disabling one of the versions with port select a get back to you.

[jmroot (Joshua Root)]

The specific variants that were problematic in that thread are not relevant to your situation. You'll have to wait for someone to fix libvlc before you'll be able to build it, but you should be able to upgrade your other ports apart from any that depend on libvlc. If others fail to build, file a separate ticket for them.

[kencu (Ken)]

will (hopefully...) be fixed when <​https://github.com/macports/macports-ports/pull/3670> is committed.

[ken-cunningham-webuse]

In 1414084014a22bff509ac1d84145f171fdef323f/macports-ports (master):

VLC, libVLC: fix build against new libx264

minor API change
closes: #58073