On Dec 5, 2003, at 1:54 AM, Martin Costabel wrote:
Blair Zajac wrote: []But the test file has a bad #include line: #include FT_ERRORS_H
This is not a bad #include line, it is just the usual freetype/freetype2 mixup.
[]| #include <freetype/freetype.h> | #include FT_ERRORS_H
Both freetype and freetype2 have headers that answer to the name <freetype/freetype.h>, and they are, of course, totally incompatible. Which one of the two is chosen depends on your good or bad luck.
Rather _ it exposes errors in the ordering of the flags : -I/sw/include should always come last.
JF
On Dec 4, 2003, at 7:35 PM, jfm wrote:
Hi Masanori,
With freetype installed, I get :
checking for freetype-config... /usr/X11R6/bin/freetype-config
checking For sufficiently new FreeType (at least 2.0.1)... no
configure: error: pangoxft Pango backend found but did not find freetype libraries
make: *** No targets specified and no makefile found. Stop.
The failing command in the config.log :
configure:24755: gcc -c -O3 -funroll-loops -fstrict-aliasing -pipe -Wall -no-cpp-precomp -DX_LOCALE -I/sw/include -I/usr/X11R6/include -I/usr/X11R6/include/freetype2 conftest.c >&5
The order of the -I flags of course explains everything..
Best,
Jean-Francois
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
