This patch correct the inclusion of freetype. Without it, ttmkfdir will not compile with freetype-2.1.7 Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 27089 [details, diff] patch to correct the inclusion of freetype
I forgot to say that this patch should be applied after ttmkfdir-3.0.9-zlib.patch Benoit
The earlier attached patch fixed build vs freetype 2.1.7, and very nicely (verified on more conservative system...) also keeps it working against 2.1.5 ;-)
Created attachment 36191 [details, diff] ft headers fix fixed ft2 headers with leastest freetype
*** Bug 63081 has been marked as a duplicate of this bug. ***
Wow, I was just about to submit a damn near identical patch to get ttmkfdir-3.0.9-r2 to compile... FWIW, I'm using GCC 3.4.1.
Created attachment 39553 [details, diff] files/ttmkfdir-3.0.9-fix-freetype217.patch This is patch from Fedora
Created attachment 39555 [details] x11-misc/ttmkfdir-3.0.9-r3.ebuild Ebuild with installed version of freetype testing.
Also required for freetype-2.1.9 users. ;) g++ -Wall -pedantic -I/usr/include/freetype2 -msse3 -fomit-frame-pointer -march=pentium4 -funroll-loops -pipe -c directory.cpp -o directory.o >/dev/null 2>&1 In file included from ttf.h:6, from ttmkfdir.cpp:8: /usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' hasn't been included yet!" /usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always use macros to include FreeType header files." /usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:" /usr/include/freetype2/freetype/freetype.h:23:2: #error " #include <ft2build.h>" /usr/include/freetype2/freetype/freetype.h:24:2: #error " #include FT_FREETYPE_H" In file included from ttmkfdir.cpp:8: ttf.h:11:31: freetype/ftmodule.h: No such file or directory libtool --mode=compile g++ -Wall -pedantic -I/usr/include/freetype2 -msse3 -fomit-frame-pointer -march=pentium4 -funroll-loops -pipe -o commandline.o -c commandline.cpp make: *** [ttmkfdir.o] Error 1 make: *** Waiting for unfinished jobs....
*** Bug 64552 has been marked as a duplicate of this bug. ***
The ebuild still fails for me after trying each of these patches. Out of curiosity, I cd'd into the work/ttmkfdir src tree and make and make install worked fine. I think the problem is just the ebuild. Either way, this is gating since I can't get around it (fresh stage 1 install).
I forgot to paste the error log: >>> emerge (1 of 6) x11-misc/ttmkfdir-3.0.9-r2 to / >>> md5 src_uri ;-) ttmkfdir-3.0.9.tar.bz2 >>> Unpacking source... >>> Unpacking ttmkfdir-3.0.9.tar.bz2 to /var/tmp/portage/ttmkfdir-3.0.9-r2/work * Applying ttmkfdir-3.0.9-cpp.patch ... [ ok ] * Applying ttmkfdir-3.0.9-zlib.patch ... [ ok ] * Applying ttmkfdir-3.0.9-ft2.patch ... [ ok ] * Applying ttmkfdir-3.0.9-gcc34.patch ... [ ok ] * Applying ttmkfdir-3.0.9-encoding.patch ... [ ok ] >>> Source unpacked. libtool --mode=compile x86_64-pc-linux-gnu-g++ -Wall -pedantic -I/usr/include/freetype2 -march=k8 -pipe -fomit-frame-pointer -o ttmkfdir.o -c ttmkfdir.cpp libtool --mode=compile x86_64-pc-linux-gnu-g++ -Wall -pedantic -I/usr/include/freetype2 -march=k8 -pipe -fomit-frame-pointer -o directory.o -c directory.cpp libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make: *** [ttmkfdir.o] Error 1 make: *** Waiting for unfinished jobs.... libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make: *** [directory.o] Error 1
Ok, got Dmitry's (#8) ebuild to work: # ACCEPT_KEYWORDS="~amd64" emerge =x11-misc/ttmkfdir-3.0.9-r3 thanks dude Pb
I did a fresh install with 2004.3 livecd for amd64. Ran into this problem. I re-emerged libtool, then re-emerged this and it worked fine.
aight devs lets wake up we have alot of work done here that really needs to be added to release branch I have noticed the same problem for the past two weeks with some ebuilds so lets wake up and add this info to the release tree so ppl dont have to hunt for fixes...
you are using a p.masked freetype, aight ? Using p.mask means it is known broken, aight ? You wouldn't be complaining about known broken stuff when you yourself chose to use it, aight ? So let's wake up to a reality you lost touch with here where your comment is utterly useless & disrespectful at best.
the patch has been added to 3.0.9-r2 , thanks all for the works here.