In file included from /usr/include/libwmf/types.h:26, from /usr/include/libwmf/api.h:25, from ie_impGraphic_WMF.cpp:37: /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" make[5]: *** [ie_impGraphic_WMF.lo] Error 1 make[5]: Leaving directory `/var/tmp/portage/abiword-2.2.7/work/abiword-2.2.7/abiword-plugins/wp/impexp/graphics/wmf/xp' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/var/tmp/portage/abiword-2.2.7/work/abiword-2.2.7/abiword-plugins/wp/impexp/graphics/wmf' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/tmp/portage/abiword-2.2.7/work/abiword-2.2.7/abiword-plugins/wp/impexp/graphics' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/abiword-2.2.7/work/abiword-2.2.7/abiword-plugins/wp/impexp' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/abiword-2.2.7/work/abiword-2.2.7/abiword-plugins/wp' make: *** [all-recursive] Error 1 !!! ERROR: app-office/abiword-2.2.7 failed. !!! Function src_compile, Line 74, Exitcode 2 Reproducible: Always Steps to Reproduce: 1. 2. 3.
You are still using XFree86?
Carsten, Well, I've got xorg-x11-6.8.2-r1 installed ... but I haven't paid any attention to whether xfree may still be invoked by startx or not ... is it a slot thing where something else needed to be reset? Since there have been no X-type problems, I haven't worried about it. Does xorg not use freetype? If not, why was Abiword's build trying to include it? /etc/X11/X links to ../../usr/X11R6/bin/Xorg. I'd thought the switch happened with the install, but since it hasn't been broken I haven't made sure. Whit
Um, no on second glance I'm definitely running xorg: # ps x | grep X 7914 ? S< 120:10 X :0 -nolisten tcp -br -deferglyphs 16 # which X /usr/bin/X # ls -l /usr/bin/X lrwxrwxrwx 1 root root 4 Apr 4 15:18 /usr/bin/X -> Xorg Used to run XFree though. Has the build fascinated on some remnant?
Um, forget X and excuse my tired eyes. The pattern looked too familiar, but in this case apparently it's not Xft.h. Which version of libwmf do you have installed?
0.2.8 I'll go to 0.2.8.2 and let you know if that fixes.
You're right. Looks like 0.2.8.2 is a pre-requisite that the ebuild doesn't know is a dependency. Thanks.
I just wonder, why you still the older lib installed. The latest stable freetype version blocks <media-libs/libwmf-0.2.8.2. Nevertheless, libwmf seems to be an missing dependency of Abiword.
Again, a good question. # emerge -p freetype These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] <www-client/mozilla-1.7.3-r3 (is blocking media-libs/freetype-2.1.9-r1) [ebuild R ] media-libs/freetype-2.1.9-r1 So although I have freetype-2.1.9-r1 installed, it's also blocked by the old mozilla (which I haven't updated since switching to firefox). Possibly I'd updated freetype with --nodeps to get around the block? I don't clearly remember, but it may have been when I was in a hurry to update firefox because of security warnings.
>Possibly I'd updated freetype with --nodeps to get around the block? That's not clean. If you (want to) update something and see a blocker, always un-emerge the blocking ebuild - or don't update at all.
Right, not clean. Thanks.
well, thanks for the help in analyzing this carlo. It is probably the --nodeps that got around the correct block that should have prevented this from happening.
