#59851 closed defect (invalid)

(10.6.8 - mt-daapd) failed to configure

Reported by: mrkapqa Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: ryandesign (Ryan Schmidt)
Port: mt-daapd libxml2 libiconv

Description (last modified by jmroot (Joshua Root))

Hello ,

i do use a small Mac with OS X 10.6.8 as a home server. Thought of accessing the iTunes shares on a Linux computer and came upon this post here


and here


the install fails on my computer

--->  Attempting to fetch mt-daapd- from https://iweb.dl.sourceforge.net/project/mt-daapd/mt-daapd/
--->  Verifying checksums for mt-daapd                                          
--->  Extracting mt-daapd
--->  Applying patches to mt-daapd
--->  Configuring mt-daapd
Error: Failed to configure mt-daapd

Attachments (1)

mtdaapd.log (8.8 KB) - added by mrkapqa 12 months ago.

Download all attachments as: .zip

Change History (7)

Changed 12 months ago by mrkapqa

Attachment: mtdaapd.log added

comment:1 Changed 12 months ago by jmroot (Joshua Root)

Cc: ryandesign added
Description: modified (diff)
Keywords: mt-daapd firefly removed
Port: libxml2 libiconv added
dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib
	  Referenced from: /opt/local/lib/libxml2.2.dylib
	  Reason: Incompatible library version: libxml2.2.dylib requires version 9.0.0 or later, but libiconv.2.dylib provides version 8.0.0

How do you have such an old libiconv? It's compatibility version 9.0.0 for me:

% otool -L /opt/local/lib/libiconv.2.dylib 
	/opt/local/lib/libiconv.2.dylib (compatibility version 9.0.0, current version 9.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.11)

comment:2 Changed 12 months ago by mrkapqa

Sorry, i don't know, but the mac is rather a recent model (macMini Server 2009) and with Snow Leopard 10.6 (NON-server version).

have not used macports for quite some time on this computer though, as it seems, and also the mpv player package could not get to install atm.

comment:3 Changed 12 months ago by jmroot (Joshua Root)

If you haven't updated your ports in over a year, you may run into issues, because we only maintain automated upgrade paths for things like renamed or replaced ports for one year. At minimum you should run sudo port selfupdate and sudo port rev-upgrade, and if that doesn't fix the problems, it may be quickest to just uninstall all ports and start again.

comment:4 Changed 12 months ago by mrkapqa

thanks, seems uninstalling and re-installing was the solution. bi´now it is installed. i did run

sudo port selfupdate

prior i think but it would not solve the issue.

comment:5 Changed 12 months ago by mrkapqa

or maybe it was

sudo port selfupgrade

sorry i cant remember it properly.


comment:6 Changed 12 months ago by mf2k (Frank Schima)

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.