Re: GTK+2.0.6 problem with Freetype



pocm mega ist utl pt (Paulo J. Matos) writes:

>  
> Hi,
> 
> > You should look at the config.log file to see the exact error messages
> > that were generated. The most likely possibility is that the
> > freetype-config from /usr/local/bin was being used, but the linker
> > found the libraries in /usr/X11R6/lib ... you may well simply
> > want to delete (make a backup first):
> > 
> >  /usr/X11R6/bin/freetype-config
> >  /usr/X11R6/lib/libfreetype.so*
> >  
> 
> I've done that, same situation happens. Now:
> pdestroy localhost:~/gnome-2.0.2rc1/gtk+-2.0.6$ which freetype-config
> /usr/local/bin/freetype-config
> pdestroy localhost:~/gnome-2.0.2rc1/gtk+-2.0.6$ freetype-config --version
> 9.1.3
> 
> I'm compiling it with gcc2.95.3, can that be the situation?

I don't think so.

> configure:14393: found /usr/local/bin/freetype-config
> configure:14406: result: /usr/local/bin/freetype-config
> configure:14417: checking for FT_New_Face in -lfreetype
> configure:14450: gcc -o conftest -g -O2 -Wall   conftest.c -lfreetype -L/usr/loc
> al/lib -lfreetype   >&5
> configure:14453: $? = 0
> configure:14456: test -s conftest
> configure:14459: $? = 0
> configure:14470: result: yes
> configure:14484: checking For sufficiently new FreeType (at least 2.0.1)
> configure:14508: gcc -c -g -O2 -Wall  -I/usr/local/include -I/usr/local/include/
> freetype2 conftest.c >&5
> configure:14489: `#include' expects "FILENAME" or <FILENAME>

This indicates that there is a problem with the freetype configuration on
your system; I'd try removing all traces of freetype and then installing
it fresh.

Regards,
                                        Owen



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]