Opened 11 years ago
Closed 11 years ago
#36969 closed defect (fixed)
minidlna: build fails with ffmpeg 1.0
| Reported by: | martin.eisenhardt@… | Owned by: | ranauei@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.2 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: | minidlna |
Description
Hi -
I just upgraded ffmpeg to the latest version (1.0.2); a subsequent upgrade of minidlna to 1.0.22_20111216_2 fails while looking for av_open_input_file in -lavformat.
I have tried to compile ffmpeg with all variants (+gpl2, +gpl3, +nonfree) enabled, with no improvement.
Please see the attached main.log of the minidlna build.
Attachments (2)
Change History (10)
Changed 11 years ago by martin.eisenhardt@…
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | martin.eisenhardt@… removed |
|---|---|
| Keywords: | minidlna ffmpeg removed |
| Owner: | changed from macports-tickets@… to ranauei@… |
| Summary: | New ffmpeg version breaks minidlna → minidlna: build fails with ffmpeg 1.0 |
comment:3 Changed 11 years ago by ranauei@…
Seems to be fixed in the latest CVS trunk of minidlna provided by #36970
comment:4 follow-up: 5 Changed 11 years ago by martin.eisenhardt@…
(First things first: Thanks for the very quick reply!)
Hmmm ... I just did
% sudo port selfupdate $ sudo port clean minidlna $ sudo port upgrade -u minidlna
This fails with
:info:configure configure: error: Could not find libavformat - part of ffmpeg
A close look at /opt/local/lib reveals
$ ls -l libavformat.* -rwxr-xr-x 1 root admin 1173012 12 Nov 22:15 libavformat.54.29.104.dylib lrwxr-xr-x 1 root admin 27 12 Nov 22:15 libavformat.54.dylib -> libavformat.54.29.104.dylib -rw-r--r-- 1 root admin 15099176 12 Nov 22:15 libavformat.a lrwxr-xr-x 1 root admin 27 12 Nov 22:15 libavformat.dylib -> libavformat.54.29.104.dylib
I do not know why the build process cannot find libavformat. Maybe you can shed some light on it.
Thanks!
comment:5 Changed 11 years ago by ranauei@…
Replying to martin.eisenhardt@…:
(First things first: Thanks for the very quick reply!)
Hmmm ... I just did
% sudo port selfupdate $ sudo port clean minidlna $ sudo port upgrade -u minidlna
Did you applied the patch to the MiniDLNA Portfile before that? I submitted the update (#36970) but is not committed yet, that means that is not available yet when you do selfupdate. If you are in hurry download the Portfile.diff attached and apply the patch yourself manually. Suppose to have the Portfile.diff in you Downloads folder and your actual directory is your non-root home, to patch the original MiniDLNA Portfile do
sudo patch -p0 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/net/minidlna/Portfile < Downloads/Portfile.diff
then if you do port info minidlna you should notice that now the version is 1.1.0_20121106 and now it should build nicely.
Changed 11 years ago by ranauei@…
| Attachment: | Portfile.diff added |
|---|
comment:6 follow-up: 7 Changed 11 years ago by martin.eisenhardt@…
Thanks again for the quick help; and no, I had not applied the patch manually. I was under the wrong impression that as soon as you commit the change to the repo it will by synced to my local ports installation using selfupdate.
The version with the patch applied compiles without problems.
One small thing, though: Up to now, the executable was called minidlna; now it is minidlnad. Small change, but easy to get confused by it if you cannot find the expected executable anymore.
Big thanks!
comment:7 Changed 11 years ago by ranauei@…
Replying to martin.eisenhardt@…:
I was under the wrong impression that as soon as you commit the change to the repo it will by synced to my local ports installation using selfupdate.
I can only submit the tickets, then is on the devs with write access to commit them eventually.
The version with the patch applied compiles without problems.
Happy to read that :D
One small thing, though: Up to now, the executable was called minidlna; now it is minidlnad. Small change, but easy to get confused by it if you cannot find the expected executable anymore.
That's something that the MiniDLNA's dev did in a recent commit.
comment:8 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Log of minidlna build