First of all thanks for a quick and kind response.

I checked; there were some libfreetype.6.dylib etc in my /sw/lib; and I
saw I had freetype2-hinting-shlibs/dev installed. I purged them, purged
texmacs, reinstalled X11.app and then tried rebiulding TeXmacs.
 
'which freetype-config' and otool gave me perfect responses.

After this procedure, I tried launching TeXmacs again, with the exact
same errormessage as before.

Any idea?




Martin Costabel skrev:

> Thøger Juul Thorsen wrote:
>
>> Yes, I should know better than updating when I'm dependent
>> on my apps working. Seems like good ol' Murphy's still
>> alive an' kicking...
>>
>> Problem: After a selfupdate and an update of a few apps,
>> including TeXmacs, I have been unable to open TeXmacs. I
>> get the following error message:
>>
>> dyld: texmacs.bin version mismatch for library:
>> /usr/X11R6/lib/libfreetype.6.dylib (compatibility version
>> of user: 10.0.0 greater than library's version: 6.3.0)
>
>
> This proves that when you built the texmacs package, it picked up
> freetype version 2.1.9 on your system, and now you don't have this
> installed any more. You can see with
>
>   otool -L /sw/lib/TeXmacs/bin/texmacs.bin
>
> where texmacs thinks it should find its freetype library.
>
> Check "which freetype-config", and if it says
> /usr/X11R6/bin/freetype-config, it should be safe to rebuild texmacs.
> You should make sure, however, that there is no file named
> "freetype-config" in /sw/bin or /usr/local/bin nor "freetype.dylib" in
> /sw/lib or /usr/local/lib.
>


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Fink-beginners mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to