Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#56390 closed defect (fixed)

strigi: build failure with ffmpeg 4

Reported by: jwhowse4 Owned by: NicosPavlov
Priority: Normal Milestone:
Component: ports Version: 2.4.3
Keywords: Cc: SickTeddyBear, dbevans (David B. Evans), jeremyhu (Jeremy Huddleston Sequoia), mf2k (Frank Schima), jjstickel (Jonathan Stickel), NicosPavlov
Port: strigi

Description

I am running an Intel Mac Pro with Sierra 10.12.6 and XCode 9.2. After upgrading ffmpeg from 3.4.2 to 4.0.0, the macports check for linking errors identifies strigi as needing to be rebuilt. The rebuild fails with errors as listed in the attached log file. Any idea what is wrong here?

Attachments (1)

strigi_main.log (734.9 KB) - added by jwhowse4 6 years ago.
strigi rebuild log file

Download all attachments as: .zip

Change History (14)

Changed 6 years ago by jwhowse4

Attachment: strigi_main.log added

strigi rebuild log file

comment:1 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)

This version of strigi is probably simply not compatible with this version of ffmpeg. Someone will have to update strigi.

comment:2 Changed 6 years ago by SickTeddyBear

Cc: SickTeddyBear added

comment:3 Changed 6 years ago by jwhowse4

As far as I can tell, strigi is a legacy component of KDE4 and development has ceased. Unfortunately the package kdelibs4 and hence all macports KDE packages depend on strigi. So it seems to me the options here are 1) hack strigi to work with the newer ffmpeg, 2) update all the macports KDE packages to a more recent version of KDE, 3) create an ffmpeg3 port which strigi depends upon. Number 3 sounds like the easiest option to me. What is your opinion?

comment:4 Changed 6 years ago by jwhowse4

I should add that version 0.7.8 is the most recent and probably final version of strigi.

comment:5 Changed 6 years ago by pmetzger (Perry E. Metzger)

At some point a newer KDE will need to be brought in, but (3) may be expedient temporarily.

comment:6 Changed 6 years ago by mf2k (Frank Schima)

Cc: dbevans jeremyhu added

Cc'ing ffmpeg maintainers for possible comment.

comment:7 Changed 6 years ago by mf2k (Frank Schima)

Cc: mf2k added

comment:8 Changed 6 years ago by jjstickel (Jonathan Stickel)

Cc: jjstickel added

comment:9 Changed 6 years ago by mf2k (Frank Schima)

Cc: NicosPavlov added

This also affects kde ports.

comment:10 Changed 6 years ago by kencu (Ken)

for right now, you can turn off ffmpeg support in strigi by putting this in the Portfile

configure.args-append  -DENABLE_FFMPEG:BOOL=OFF

or activate the older version of ffmpeg assuming you still have it installed.

presumably someone somewhere will update strigi for the deprecated (and now apparently deleted) ffmpeg API that it is using.

Maybe there is some other way to turn on the older ffmpeg behaviour with a cpp define -- haven't looked into that.

comment:11 Changed 6 years ago by NicosPavlov

The API used by strigi is mostly still present, it seems to be just one variable that is problematic. I patched the code to have it compile.

comment:12 Changed 6 years ago by NicosPavlov

Owner: set to NicosPavlov
Resolution: fixed
Status: newclosed

In fddc54476e4f27c908cdf6d0316653be2f87c0d9/macports-ports (master):

strigi: update ffmpeg variables to use more recent API, remove deprecated variable (fixes #56390)

comment:13 Changed 6 years ago by mf2k (Frank Schima)

Summary: strigi rebuild fails after ffmpeg updatestrigi: build failure with ffmpeg 4
Note: See TracTickets for help on using tickets.