xorg-server-1.5.3-r1 will not compile with libXfont >= 1.4.0, since it doesn't have fontmod.h This is an "old" version of xorg-server, but since functionality has been removed from >=1.6 (xsecurity extension), for some uses it is still crucial. Works fine if >=x11-libs/libXfont-1.4.0 is masked. libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../../include -I../../../hw/xfree86 -I../../../hw/xfree86/include -I../../../hw/xfree86/common -I../../../hw/xfree86/os-support -I../../../hw/xfree86/os-support/bus -I../../../os -I./../ddc -I./../i2c -I./../loader -I./../rac -I./../parser -I./../vbe -I./../int10 -I./../vgahw -I./../dixmods/extmod -DHAVE_DIX_CONFIG_H -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I../../../include -I../../../include -I../../../Xext -I../../../composite -I../../../damageext -I../../../xfixes -I../../../Xi -I../../../mi -I../../../miext/shadow -I../../../miext/damage -I../../../render -I../../../randr -I../../../fb -DHAVE_XORG_CONFIG_H -DXF86PM -DHAVE_ACPI -O2 -pipe -march=native -MT xf86Bus.lo -MD -MP -MF .deps/xf86Bus.Tpo -c xf86Bus.c -fPIC -DPIC -o .libs/xf86Bus.o In file included from xf86Configure.c:41: ./../loader/loaderProcs.h:59:31: error: X11/fonts/fontmod.h: No such file or directory In file included from xf86Configure.c:41: ./../loader/loaderProcs.h:90: error: expected ‘)’ before ‘*’ token
I'm tempted to mark this as invalid, following bug 237778.
(In reply to comment #1) > I'm tempted to mark this as invalid, > following bug 237778. > What's invalid? That there's an ebuild in the repos that just needs the dependencies updated? It's still in the repos because some people NEED xsec, even if philosophically some think it sucks. But that's irrelevant -- the engineering problem exists, there's no engineering reason why one must update, and there's a very easy engineering solution. Maybe "Won't fix because it would take 30 seconds to make the fix" would at least be a logical response. Which would be fine -- anyone with the problem could at least find it on the bug report and add the mask, thereby saving noise since at least the bug won't be reported again. But invalid implies the bug never existed -- which just doesn't make a lick of sense.
Well, let's see what xorg team says, but I doubt xorg-server will stay for long anyway (at least not for this reason - the other bug was a WONTFIX)
that was meant to be "xorg-server 1.5.3".
1.5.3-r1 is no longer in portage. 1.5.3-r6 is and is patched to work with libXfont 1.4. Please upgrade. Thanks
(In reply to comment #5) > 1.5.3-r1 is no longer in portage. 1.5.3-r6 is and is patched to work with > libXfont 1.4. > > Please upgrade. > > Thanks > Ah, hadn't seen it had been pulled from the tree. Can't upgrade, r6 doesn't work for me. Fortunately, I've kept a backup around -- which causes confusion. But since gentoo apparently is taking a policy of code churn, I guess I'll just have to adapt or abandon; I think three forks of the rsync tree is probably my limit.
