I try to emerge gtk+ but it complains about Xft Pango. I don't understand exacly what's going on. I have tried re-emerging xorg-x11 but that doesn't seem to work. checking return type of signal handlers... (cached) void checking for x86 platform... no checking for freetype-config... /usr/bin/freetype-config checking For sufficiently new FreeType (at least 2.0.1)... yes configure: error: Xft Pango backend is required for x11 target !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/gtk+-2.6.4/work/gtk+-2.6.4/config.log !!! ERROR: x11-libs/gtk+-2.6.4 failed. !!! Function econf, Line 485, Exitcode 0 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message. Reproducible: Always Steps to Reproduce: 1. emerge gtk+ Actual Results: gtk+ fails to configure Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r0, 2.6.11-gentoo-r3 x86_64) ================================================================= System uname: 2.6.11-gentoo-r3 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.10 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Feb 20 2005, 22:32:21)] dev-lang/python: 2.3.5 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.9.5, 1.5, 1.8.5-r3, 1.6.3, 1.7.9-r1, 1.4_p6 sys-devel/binutils: 2.15.92.0.2-r6 sys-devel/libtool: 1.5.10-r5 virtual/os-headers: 2.6.8.1-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-march=athlon64 -O3 -fomit-frame-pointer -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O3 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig buildpkg ccache distlocks fixpackages sandbox usersandbox" GENTOO_MIRRORS="http://mirror.switch.ch/mirror/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://linuv.uv.es/mirror/gentoo/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.es.gentoo.org/gentoo-portage" USE="amd64 X a52 aac aalib acpi alsa apache2 avi bash-completion berkdb bitmap-fonts bluetooth bzlib cdparanoia cdr crypt cups curl dga dio directfb divx4linux dv dvd dvdr dvdread encode ethereal fastcgi fbcon ffmpeg fftw flac font-server foomaticdb fortran ftp ggi gif glut gpm gstreamer gtk gtk2 hal icq imagemnagick imlib ipv6 java javascript jp2 jpeg junit kde lm_sensors lzw lzw-tiff mad matroska mime mng motif mozilla mp3 mpeg msn multilib ncurses nls nocd nptl nptlonly offensive ogg oggvorbis openal opengl oss pam pdflib perl png posix python qt quicktime readline samba sdl sockets source spell ssl szip tcltk tcpd tiff truetype truetype-fonts type1-fonts unicode usb userlocales v4l vcd xine xml xml2 xmms xosd xpm xrandr xv xvid zlib video_cards_ati linguas_es linguas_el" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Created attachment 53695 [details] gtk+ config.log
What freetype version do you have? The gtk+ ebuild depends on pango 1.8.0, but probably should depend on a engine for pango to run on aswell, since you seem to have installed pango without the needed engine under it successfully.
Found the solution at http://forums.gentoo.org/viewtopic-t-297910-start-0-postdays-0-postorder-asc-highlight-.html The pango ebuild *must* be compiled with the following global varialbes: export PKG_CONFIG_DIR=/usr/lib64/pkgconfig export PKG_CONFIG_PATH=/usr/lib64/pkgconfig After having those global variables set, having re-emerged pango, gtk+ will compile flawlessly. Request: Please, modify the pango ebuild so it'll set those paths.
i'm pretty sure this is a dupe.
It might be a dupe, but it isn't fixed :(
Is this still a problem? If so please post the output of ls -ld /usr/lib*
This problem also appears with my P3 installation. Workaround is to first install freetype, then install pango. As a result, gtk will compile.
I have this problem too. When /usr/lib !-> /usr/lib64, xorg-x11 installs its pkgconfig files in lib64 unlike any other ebuild, and hence the discontinuity that shows up with pango builds. It is up to the maintainers to decide the correct solution, but it seems like specifying the paths in the pango ebuild is more of a hack around the source of the problem than pkgconfig not being told in its ebuild to be set to look in all the right places (lib64), or xorg installing its pkgconfig files in lib64. That is my take anyway - adjusting pkg-config was my local fix, because I did not feel like messing with X.
Is this bug fixed?
(In reply to comment #9) > Is this bug fixed? Yes. pkg-config's compile time default is set to /usr/lib64/pkgconfig (on multilib arches only of course) in its latest version.
