my rsync is broken, anyone got a leopard one?

[jlm at justinfront.net]

Jeremy

My cd drive has not worked for most of the life of this machine.  It  
seems a common suggestion to reinstall leopard when there is a  
problem, as far as I am concerned that is completely impractical I  
doubt I even still have the CD's and there is too much in the way that  
it's setup, and not something I would consider, seriously I reinstall  
windows when it breaks... macs you can normally fix, I am more likely  
to find an alternative approach to macport than reinstall my system.  
Maybe installing linux instead when it gets too hard to keep this  
leopard alive.

Can anyone suggest how I can fix libiconv-24 or what ever the files  
are, is no one running a leopard that can send me privately some  
replacement files?  Or suggest how I might 'upgrade' this aspect of my  
system?

Best Justin

On 24 Aug 2013, at 18:00, Jeremy Huddleston Sequoia wrote:

>
> On Aug 24, 2013, at 7:27, Joshua Root <jmr at macports.org> wrote:
>
>> On 2013-8-25 00:17 , jlm at justinfront.net wrote:
>>> Hi my rsync seems to be broken I can't selfupdate macports does  
>>> anyone
>>> have a copy of rsync that would work for leopard?
>>>
>>> This is the error I get.
>>>
>>> port -v selfupdate
>>> --->  Updating MacPorts base sources using rsync
>>> dyld: lazy symbol binding failed: Symbol not found: _locale_charset
>>> Referenced from: /usr/bin/rsync
>>> Expected in: /usr/lib/libiconv.2.dylib
>>>
>>> dyld: Symbol not found: _locale_charset
>>> Referenced from: /usr/bin/rsync
>>> Expected in: /usr/lib/libiconv.2.dylib
>>>
>>> I tried getting a git of rsync and building rsync myself but it  
>>> would
>>> not make.
>>
>> Are you sure it's not your libiconv that's broken? Installing the  
>> 10.5.8
>> combo updater should restore rsync anyway.
>
> Yeah, you should never clobber your OS files.  It looks as though  
> your libiconv was clobbered.  10.5.0 and 10.5.8 both had libiconv-24  
> (see http://opensource.apple.com), so it's likely that the combo  
> update won't restore your libiconv, but give it a shot anyways.  If  
> it doesn't work, your best bet is to reinstall your OS because you  
> may have clobbered other files as well.
>
> If you're sure it's just libiconv.dylib that you clobbered, you can  
> get it off of the install media (just copy over the one file).
>
> --Jeremy
>
>
>