Alexander K. Hansen wrote:
Remind me about the error message and the workaround and I'll add an entry--hopefully by this evening (GMT-5).

I am dumping a collection of error messages on you without trying to formulate it as FAQ Q/A. The first one or two lines of each error message should be suffiently characteristic, I guess.


Here is a collection of recently appearing errors that come from the fact that <freetype/freetype.h> can be resolved by /sw/include/freetype/freetype.h
instead of the intended
/usr/X11R6/include/freetype2/freetype/freetype.h
(We can discard the third possibility of
/sw/include/freetype2/freetype/freetype.h, because this shouldn't exist any more, and it would give different error messages anyway.)


The workaround is to remove the freetype and freetype-hinting packages (at most one of these two is installed, but "fink remove freetype freetype-hinting" will remove whatever is installed). They are buildonly packages anyway and can always be safely removed.

A fix in fink would be to force -I/usr/X11R6/include/freetype2 before -I/sw/include in all the concerned packages, but this is hard to achieve, and it actually is a workaround, too. The real fix would be to lean on the freetype2 guys to make them fix the upstream sources. Why for god's sake did they have to put a "freetype" directory inside include/freetype2? This header file should be named <freetype2/freetype.h>.

Here is a first error, fom the compilation of librsvg2:

/sw/include/pango-1.0/pango/pangoft2.h:52: error: parse error before '*' token
/sw/include/pango-1.0/pango/pangoft2.h:57: error: parse error before '*' token
/sw/include/pango-1.0/pango/pangoft2.h:61: error: parse error before '*' token
/sw/include/pango-1.0/pango/pangoft2.h:86: error: parse error before 
"pango_ft2_font_get_face"
/sw/include/pango-1.0/pango/pangoft2.h:86: warning: data definition has no type or 
storage class
make[2]: *** [rsvg-gz.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive-am] Error 2
### execution of make failed, exit code 2
Failed: compiling librsvg2-2.4.0-3 failed

Here is another one, from the compilation of vte:


In file included from vteft2.c:32:
vteglyph.h:64: error: parse error before "FT_Library"
vteglyph.h:64: warning: no semicolon at end of struct or union
vteft2.c: In function `_vte_ft2_get_text_width':
vteft2.c:236: error: dereferencing pointer to incomplete type
vteft2.c: In function `_vte_ft2_get_text_height':
vteft2.c:244: error: dereferencing pointer to incomplete type
vteft2.c: In function `_vte_ft2_get_text_ascent':
vteft2.c:252: error: dereferencing pointer to incomplete type
vteft2.c: In function `_vte_ft2_draw_text':
vteft2.c:294: error: dereferencing pointer to incomplete type
vteft2.c:295: error: dereferencing pointer to incomplete type
make[2]: *** [vteft2.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
### execution of make failed, exit code 2
Failed: compiling vte-0.11.10-3 failed

Here is yet another one, from gtk+2 (maybe fixed in the meantime?)


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.
### execution of LD_TWOLEVEL_NAMESPACE=1 failed, exit code 2
Failed: compiling gtk+2-2.2.4-2 failed

On the other hand, the suspiciously similar-looking


ld: Undefined symbols:
_FT_Access_Frame

is not a freetype vs freetype2 mixup, but a mixup between two versions of freetype2. It appears in two situations:


When it says something like

dyld: klines Undefined symbols:
/sw/lib/libqt-mt.3.dylib undefined reference to _FT_Access_Frame

it is a symptom of a version of qt3 compiled under xfree-4.2.1 that won't work with Apple's X11 on Panther. Workaround: Rebuild or bbraun's unofficial bindist.


When it is the first form above, encountered for example in the compilation of pango1-xft2, it is probably caused by a leftover from an older installation of X11 and can be fixed by reinstalling X11SDK.pkg (one instance of the "lazy installer syndrome").

--
Martin












------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to