wine users - Jun 2002 - FreeType 2.1.2

I upgraded FreeType to 2.1.2 and it broke WINE.

Is there a simple way to link WINE to: "libfreetype.so.6.3.0" rather 
than: "libfreetype.so.6"?

Or, is there some other way to fix it?

--
JRT

--- James Richard Tyrer <tyrerj@acm.org> wrote:
> I upgraded FreeType to 2.1.2 and it broke WINE.
> 
> Is there a simple way to link WINE to:
> "libfreetype.so.6.3.0" rather 
> than: "libfreetype.so.6"?
> 
> Or, is there some other way to fix it?
I'm not an a bin expert in this.
I can think of:
a) creating a symbolic link for the library name,
required by Wine
b) recompiling Wine

Andriy

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Andriy Palamarchuk wrote:
> --- James Richard Tyrer <tyrerj@acm.org> wrote:
> [skipped]
> 
>>No the problem is that compiling WINE resluts in it
>>being linked against 
>>that link: "libfreetype.so.6" and I need WINE linked
>>against the actuall 
>>library name: "libfreetype.so.6.3.0" so that I can
>>upgrade FreeType and 
>>WINE will continue to use the older version.
> 
> 
> One more (maybe silly ;-) suggestion - did you try to
> remove the link ".so.6", rerun Wine configure,
> reinstall Wine. I wonder if configure will pick up the
> library name ".so.6.3.0" in this case.
> 
It got it fixed

I edited the: "config.cache" file and changed the version number for: 
"libfreetype".  Ran: "configure", "make clean" and
then ran the script
again.  It works so what ever piece calls: "libfreetype" must be
getting
the correct version.

--
JRT