When I emerge grass, configure fails when looking for freetype.h. Here is the log : checking whether to use FreeType... yes checking for location of FreeType includes... checking for freetype/freetype.h... no configure: error: *** Unable to locate FreeType includes. !!! ERROR: app-misc/grass-5.0.2 failed. !!! Function src_compile, Line 92, Exitcode 1 !!! ./configure failed
I forgot to tell that Freetype 2 is already emerged...
If I tell emerge USE="-truetype", then emerging grass is OK. Btw. includes for freetype are included in /usr/include/freetype2/freetype !
It looks like grass-5.0.2 only supports freetype2. From the requirements.html file in the grass-5.0.2 tarball: Optional Requirements ..... FreeType2 (for d.text.freetype) However, if we don't specify where the freetype2 header files are then either the configure script will fail with the above error or, if freetype-1.3.x is installed, the following error is encountered in the grass compile: GISGEN: src/display/d.text.freetype - Sat Sep 6 20:15:48 NZST 2003 ######################################################## /var/tmp/portage/grass-5.0.2/work/grass5.0.2/src/display/d.text.freetype mkdir OBJ.i686-pc-linux-gnu make -f OBJ.i686-pc-linux-gnu/make.rules make[1]: Entering directory `/var/tmp/portage/grass-5.0.2/work/grass5.0.2/src/display/d.text.freetype' gcc -I/var/tmp/portage/grass-5.0.2/work/grass5.0.2/src/include -march=pentium4 -O2 -pipe -fomit-frame-pointer -c main.c -o OBJ.i686-pc-linux-gnu/main.o main.c:75: parse error before "library" main.c:76: parse error before "face" ..... make[1]: *** [OBJ.i686-pc-linux-gnu/main.o] Error 1 make[1]: Leaving directory `/var/tmp/portage/grass-5.0.2/work/grass5.0.2/src/display/d.text.freetype' GISGEN failure at STEP: src/display/d.text.freetype In fact the d.text.freetype README file instructs us to specify where the freetype2 files are installed. Adding the following to the grass-5.0.2 ebuild fixes things nicely: use truetype \ && myconf="${myconf} --with-freetype \ --with-freetype-includes=/usr/include/freetype2" \ || myconf="${myconf} --without-freetype"
thx, fixed :)
forgot to close...
Was this really fixed in 2003? I got the error now. What was the fix? Where did it go?
