#45822: Issues when installing VLC-devel in a clean MacPorts install --------------------------------+-------------------------------- Reporter: onaforeignshore@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: VLC-devel | --------------------------------+-------------------------------- Comment (by rjvbertin@…): As Mojca pointed out, the current VLC-devel port is outdated, and build failures like this are the sort of thing that can happen when a port hasn't been maintained for a certain time. I have pointed Mojca to an updated VLC-devel port but I'm not aware that it has already been committed into the official port repository. At this point I see 2 things you could do: 1) If you're mostly interested in getting the VLC version provided by port :VLC-devel you could edit the port file (`sudo port edit VLC-devel`) and rename the `quartz` variant to something like `native`. Be sure to rename all occurrences! Also, check beforehand if the name you chose doesn't exist as a variant in any of VLC's dependencies (or just pick something that's highly unlikely to exist as a variant name in any port). This will test the hypothesis that you are running into variant conflicts due to propagation of the quartz variant. NOTE however that there's absolutely no guarantee that the outdated port will build even when all its dependencies have been installed successfully. EDIT: it's not impossible that the `+qtkit` variant also leads to conflicts through propagation, though that shouldn't be because of `port:py27-cairo` because that port doesn't have any variants as far as I can see. 2) if you're interested to help figure out why this is happening to you, you could clean MacPorts again (or at least remove everything that was pulled in for building VLC-devel) and then install `port:VLC` with the variants that interest you. Should you run into a similar issue building `port:VLC` you should report it (probably in a new ticket referring this one), but in that case I'd also urge you to try the potential solution described under 1). -- Ticket URL: <https://trac.macports.org/ticket/45822#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X