emerge claims that xft conflicts with xfree. When would you ever run it without xfree? Here is the error I get: --- maze root # emerge xft Calculating dependencies ...done! !!! Error: the >=x11-base/xfree-4.3.0-r2 package conflicts with this package and both can't be installed on the same system together. --- Emerge info output: Portage 2.0.48-r1 (default-x86-1.4, gcc-3.2.2, glibc-2.2.5-r4,2.3.1-r4) ================================================================= System uname: 2.4.20-gentoo-r2 i686 AMD Athlon(tm) Processor GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ ftp://mirror.iawnet.sandia.gov/pub/gentoo/" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gtkhtml gdbm berkdb slang readline tetex svga tcltk java guile X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl -arts aalib acpi alsa bonobo canna cdr cjk dga directfb dvd fbcon freewnn ggi gphoto2 imap jack ladcca lcms ldap maildir mozilla nas pda sasl sse usb" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-mcpu=i686 -O3 -pipe" CXXFLAGS="-O2 -mcpu=i686 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
xfree-4.3.0-r2 and up includes xft, you don't need to emerge the x11-libs/xft package thats only useful for older xfree's.
No, this is not invalid. I think this is stupid. Please look at Bug 24111 to see why I would like to try emerging this package. Will I break xfree if I do so? I doubt it. At one time, the version of XFT with xfree was broken too. What would I do then? Wait for the next version of xfree? In the event that I wish to emerge XFT over the xfree version of XFT, I should be able to. It seems emerge doesnt have a "force" facility. Short of fiddling inside the guts of various portage files, I am again stuck. It seems particulary dumb to have two versions of XFT, with one of them rolled into a package that takes an age and a day to compile, not to mention severly perturbing my system state. If the two versions of XFT are so incompatible that X will not work with the seperate version, please consider that you have created a situation where other developers can now create ebuilds that only build against the version of XFT that they have. I think I am in just such a bind. Again, please look at Bug 24111 . I am not sure if XFT is the problem, but I can't test that now, can I? Please reconsider your position. Either those two versions of XFT must co-exist with each other peacefully, or one of them should be removed.
From what I know xft is now PART of xfree as previously was PART of fontconfig. xfree has xft in it's tree and you can get improved/mantained version of xft from xfree, please upgrade your xfree and fontconfig.
I can actually tell you that your avifile problem was most likely not related to the build of xfree or fontconfig. The compile line in comment #1 there fails to include -lfontconfig and that results in the missing symbols. I'm not sure why this happens and later on it doesn't (it is non-reproducable), but it's a configure side problem, nothing todo with the compiled packages directly. You are not supposed to have both versions (ebuild & xfree) of xft2 around, the initial xft2 package was only meant to make room for a smooth upgrade phase from xft1 to xft2 when it wasn't in any official xfree release. It was always meant to be replaced in time with the xft2 sources in the xfree tree.
