Hi, I'm using ~x86 and the hardmasked xorg-x11-6.7.99.903 (don't think this problem is related to that that). When I try to emerge x11-drm-20040827 with VIDEO_CARDS="mach64" I get errors which look like they are related to koutput: In file included from /var/tmp/portage/x11-drm-20040827/work/drm/mach64_drv.c:30: /usr/src/linux-2.6.8.1/include/linux/config.h:4:28: linux/autoconf.h: No such file or directory but of course linux/autoconf.h is /var/tmp/kernel-output/2.6.8.1/include/linux/autoconf.h I think that the build process is looking for /usr/src/linux/include/linux/autoconf.h which doesn't exist. FWIW, on a different system using kernel 2.4, I can build x11-drm with VIDEO_CARDS="radeon mach64" with no problems (and of course no koutput). I will attach the build log. Here is my emerge info: Gentoo Base System version 1.5.3 Portage 2.0.50-r10 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.8.1) ================================================================= System uname: 2.6.8.1 i686 Celeron (Coppermine) distcc 2.17 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /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="-O3 -march=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d alsa apm arts berkdb cdr cjk crypt cups dga dvd emacs encode esd f77 faad fbcon fftw flac gcj gdbm gif gimpprint ginac gnome gpm gstreamer gtk gtk2 imlib jack jpeg leim libg++ libwww lirc live mad matroska mikmod mmx mng motif mozilla mpeg ncurses nls objc offensive oggvorbis opengl oss pam pdflib perl plotutils png ppds python qhull qt quicktime radeon readline scanner sdk sdl slang speex spell sse ssl svg tcpd tetex theora tiff truetype usb v4l video_cards_mach64 wxwindows x86 xinerama xml xml2 xmms xosd xv xvid zlib"
Created attachment 38775 [details] log of attempting to install x11-drm
I'm not sure if this is due to the four-number (2.6.8.1) versioning or what. I'll ask around about koutput/kernel-2 specifics.
What happened to the good 'ol days when a borked kernel meant a new FULL version number the next day! :) Hmmm, the ~x86 kernel was 2.6.9-rc1 but I went with the x86 kernel (2.6.8.1). I wonder if there would also be a problem with the -rc1 and those type of kernels? I may try with 2.6.9-rc1 if I have time -- or we can wait for 2.6.9 to come out for real.
I'm now using 2.6.9-rc1. Still has the same problem.
Can you try it with one of those kernels not using koutput? The koutput stuff might be broken right now wrt 2.6.8.1.
I will try building my kernel without koutput later today. BTW, I found that this bug is not specific to mach64: I tried it with VIDEO_CARDS set to radeon and to i810. Both cause the same errors.
Works fine with both 2.6.8.1 and 2.6.9-rc1 *without* koutput (well it emerges cleanly anyway, still don't have DRI working). I guess I'll stop using koutput for now (also because of 63103)
koutput is depreciated and no longer used maintained. This is because of the build system fixes that the kernel developers commited to the 2.6.6 kernel. As as result, it is no longer supported by Gentoo Mobile team. Below is the post to gentoo-dev mailing list by the creator of the koutput system. Hey all, Been busy with lots of other things, and dreading sending this anyway, but I wanted to clear things up Re: the koutput/kbuild stuff that I'd worked on to fix some problems previously related to 2.6 kernel build issues. Unfortunately, the fix that was 95% implemented, and had the beginnings of code in the tree got ham-strung by a combination of kernel stuff changing under my/our feet, and Real Life (tm) things coming in at just the wrong time. As a result, the kmod.eclass, and config-kernel have several problems, and are only 1/2 implemented anyway. Sooo, don't use kmod.eclass. Just don't. config-kernel i will be package.masking as well soon. I know there are a few ebuilds out there that currently use kmod.eclass for a few things. I'll be contacting those maintainers over the next few days to address things with them, and get them sorted out with how to get things working with 2.6.6 and newer kernels. If you get any bugs from people complaining about such and such ebuild not working with koutput, assing or CC me, and i'll deal with it. Thanks. Sorry for any confusion folks. -pete
Bryan, what's the deal with x11-drm under 2.6? Is it working w/ just M= now?
The 20040827 snapshot does work properly with M=. With sandboxing and the deprecation of koutput, it will not work with kernels older than 2.6.6, though. Bug #68453 is related to this and updates the 0827 snapshot ebuild to reflect the deprecation of koutput (and the kmod eclass).
This should be a quick close out and solution... Especially since we're coming closer and closer to killing kmod.
I kmod dead? Can I close this? It certainly isn't affecting me anymore
Right, koutput is gone forever.
