minidlna @1.3.0 could not find libid3tag
:info:configure checking for id3_file_open in -lid3tag -lz... yes
:info:configure configure: error: Could not find libid3tag
:info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_minidlna/minidlna/work/minidlna-1.3.0" && ./configure --prefix=/opt/local
:info:configure Exit code: 1
:error:configure Failed to configure minidlna, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_minidlna/minidlna/work/minidlna-1.3.0/config.log
:error:configure Failed to configure minidlna: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure while executing
:debug:configure "$procedure $targetname"
Change History (5)
| Cc: |
ranauei@… removed
|
| Owner: |
set to ranauei@…
|
| Port: |
minidlna added
|
| Status: |
new →
assigned
|
| Owner: |
changed from ranauei@… to ryandesign
|
| Status: |
assigned →
accepted
|
| Resolution: |
→ fixed
|
| Status: |
accepted →
closed
|
This is happening because the port is regenerating the configure script with autoreconf. Something changed between autoconf 2.69 and autoconf 2.71 that this project's configure.ac was not anticipating, making it erroneously think libid3tag wasn't found even though it was. I reported the problem to the developers: https://sourceforge.net/p/minidlna/bugs/341/
I'll fix it by having the port no longer use autoreconf. The reason why the port was using autoreconf in the first place was because when I added the port ten years ago it was fetching from CVS and presumably CVS did not contain the generated configure script, but this port hasn't been fetching from CVS for a long time.