Incompatible library version: rsync requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0

[ash@…]

A fresh install of Macports v1.8.0 on Snow Leopard with version @3.0.6 yields the following error when utilising the ssh remote option: -

$ rsync -vax -e ssh user@remote.host:/path/ /local/path/

dyld: Library not loaded: /opt/local/lib/libiconv.2.dylib
  Referenced from: /opt/local/bin/rsync
  Reason: Incompatible library version: rsync requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: unexplained error (code 255) at io.c(600) [receiver=3.0.6]

[jmroot (Joshua Root)]

What is the output from these commands?

otool -L /opt/local/lib/libiconv.2.dylib
lipo -info /opt/local/lib/libiconv.2.dylib

[ash@…]

Replying to jmr@…:

What is the output from these commands?

otool -L /opt/local/lib/libiconv.2.dylib
lipo -info /opt/local/lib/libiconv.2.dylib

$ otool -L /opt/local/lib/libiconv.2.dylib 
/opt/local/lib/libiconv.2.dylib:
	/opt/local/lib/libiconv.2.dylib (compatibility version 8.0.0, current version 8.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)

$ lipo -info /opt/local/lib/libiconv.2.dylib 
Non-fat file: /opt/local/lib/libiconv.2.dylib is architecture: x86_64

[ryandesign (Ryan Carsten Schmidt)]

This error usually occurs when a program was built to use the MacPorts libiconv, but the MacPorts libiconv is in some way unsuitable (for example, wrong architecture), so the library of the same name provided by Apple in /usr/lib is used instead, but that library has compatibility version 7.0.0 whereas the MacPorts one has compatibility version 8.0.0 so things fail.

What is the architecture of /opt/local/bin/rsync?

[ash@…]

hi, sorry for the delay.. i haven't had access to the machine in question, i will in the next day so i'll update then.. sorry!

[ash@…]

i completely removed /opt and ensured my environment was clean and re-installed macports fresh after a reboot and have not experienced the problem again. thanks for the time spent on this one, apologies.