Bug 77268 – emerge xorg-x11 fails: No rule to make target `includes' in xc/programs/Xserver/hw/xfree86/drivers/i810

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Jeff Turley 2005-01-09 12:50:14 UTC]

When I try to emerge xorg-x11, it fails during the compile phase, citing line 626 of src_compile.  The first build error seems to be this:

make[6]: Entering directory `/var/tmp/portage/xorg-x11-6.8.0-r3/work/xc/programs/Xserver/hw/xfree86/drivers/i810'
make[6]: *** No rule to make target `includes'.  Stop.

interesting that I'm not using an i810 chipset at all...

Reproducible: Always
Steps to Reproduce:
1. # emerge xorg-x11
Actual Results:  
Complile crashed out citing this error:
Function src_compile, Line 626, Exitcode 2
(no error message)

Expected Results:  
Complete the build and install x.0rg

System Configuration:
AMD AthlonXP 2800+ (?)
ATi Radeon 9000 Pro
some Via chipset
AC'97 sound (not configured yet)

tux portage # emerge info
Portage 2.0.51-r2 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040808-r1,
2.4.28-gentoo-r4 i686)
=================================================================
System uname: 2.4.28-gentoo-r4 i686 AMD Athlon(tm) XP 2500+
Gentoo Base System version 1.4.16
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.14.90.0.8-r1
Headers:  sys-kernel/linux-headers-2.4.21-r1
Libtools: sys-devel/libtool-1.5.2-r5
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X acl alsa apm arts avi berkdb bitmap-fonts cdr crypt cups dvd encode
foomaticdb fortran gdbm gif gnome gpm gtk2 ipv6 jpeg kde libwww mad mikmod motif
mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime
readline sdl spell ssl svga tcpd truetype xml2 xmms xv zlib"


tux portage # gcc --version
gcc (GCC) 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[Comment 1 Jeff Turley 2005-01-09 12:56:20 UTC]

Created attachment 48043 [details]
output of '# emerge xorg-x11'

I think only the end of this file is useful, but I've included my whole SSh
buffer just in case.  Unfortunately, the SSh buffer is too small to grab the
whole compile process off of.

[Comment 2 Adam Jackson 2005-01-09 14:59:48 UTC]

please attach the following files:

/var/tmp/portage/xorg-x11-6.8.0-r3/work/xc/lib/Xdmcp/Makefile
/var/tmp/portage/xorg-x11-6.8.0-r3/work/xc/config/cf/host.def

[Comment 3 Jeff Turley 2005-01-09 15:07:50 UTC]

Created attachment 48056 [details]
/var/tmp/portage/xorg-x11-6.8.0-r3/work/xc/lib/Xdmcp/Makefile

[Comment 4 Jeff Turley 2005-01-09 15:09:10 UTC]

Created attachment 48058 [details]
/var/tmp/portage/xorg-x11-6.8.0-r3/work/xc/config/cf/host.def

[Comment 5 Adam Jackson 2005-01-09 15:25:23 UTC]

yikes, there is no way that should be happening.  note that the log you attached failed in lib/Xdmcp, not the i810 driver.  if it stops at different places each time i'm tempted to blame bad hardware.  does it?

[Comment 6 Jeff Turley 2005-01-09 15:42:54 UTC]

::grumble:: Ran it again and it threw that "No rule to make target 'includes'" error again.  This time it was here:

make[3]: Entering directory `/var/tmp/portage/xorg-x11-6.8.0-r3/work/xc/lib/XprintAppUtil'

different directory... but its still Function src_compile, Line 626, Exitcode 2.

So, what does bad hardware mean?  I have little doubt that the ram I have is cruddy.

[Comment 7 Donnie Berkholz (RETIRED) 2005-01-09 15:45:57 UTC]

*** This bug has been marked as a duplicate of 20600 ***