Trouble with subversion

Ryan Schmidt ryandesign at macports.org
Mon May 14 13:36:37 PDT 2007


On May 14, 2007, at 14:34, Andre-John Mas wrote:

> On 14-May-07, at 14:24 , Ryan Schmidt wrote:
>
>>> zanniati:/Users/ajmas root# otool -L /opt/local/lib/libiconv.2.dylib
>>> /opt/local/lib/libiconv.2.dylib:
>>>         /opt/local/lib/libiconv.2.dylib (compatibility version  
>>> 7.0.0, current version 7.0.0)
>>>         /usr/lib/libmx.A.dylib (compatibility version 1.0.0,  
>>> current version 92.0.0)
>>>         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,  
>>> current version 88.1.9)
>>
>> Where the heck is libmx coming from? I get
>>
>> $ otool -L /opt/local/lib/libiconv.2.dylib
>> /opt/local/lib/libiconv.2.dylib:
>>         /opt/local/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.1.7)
>>
>> on PowerPC and
>>
>> $ otool -L /opt/local/lib/libiconv.2.dylib
>> /opt/local/lib/libiconv.2.dylib:
>>         /opt/local/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.7)
>>
>> on Intel.
>
> Wish I could answer that, since on my Intel MacBook Pro	I get:
>
> s$ otool -L /opt/local/lib/libiconv.2.dylib
> /opt/local/lib/libiconv.2.dylib:
>         /opt/local/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.4)
>
> What is libmx? I find it is installed in /usr/lib. Things are  
> working since I corrected
> I removed LD_LIBRARY_PATH.

Maybe having LD_LIBRARY_PATH set influenced which libraries it chose  
to link with at compile time. Whatever. If software that uses  
libiconv works for you, then I guess it's ok.





More information about the macports-users mailing list