On Jan 18, 2009, at 7:52 PM, Mojca Miklavec wrote:
Hello Thomas,
I'm guessing blindly. Can you please try
which rsync otool -L /wherever/is/rsync
and check if all the libraries exist. On my machine I have:
/usr/bin/rsync: /usr/lib/libiconv.2.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.11)
/sw/bin/rsync: /sw/lib/libpopt.0.dylib (compatibility version 1.0.0, current version 1.0.0) /sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.10)
The versions 5 and 7 seem suspiciosly similar to reports that your system complains about. Does rsync work OK for simple commands?
Hi Mojca, yes, rsync works normally for simple commands (that's how I get the first-setup.sh). My rsync is the normal system one in /usr/bin: /usr/bin/rsync: /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.1)
You're still using 10.4, right? So could this be the reason? Thomas