On systems with the sys-kernel/config-kernel installed (for out-of-kernel-modules support) and kernel output configured to go to /var/tmp/kernel-output/ the installation of alsa-drivers fails because 'include/linux/version.h' could not be found anymore. This file is normally created during the kernel compilation, but with the config-kernel installed this appears up in the kernel's output tree instead of the source tree (/usr/src/linux). A quick hack to add copy the contents of the kernel output directory to the sandbox makes it work, but I'm not confident that this the preferred way to go. latexer, eradicator, please comment. Reproducible: Always Steps to Reproduce: 1. 2. 3. sys-kernel/config-kernel 0.3.3 media-sound/alsa-driver 1.0.6a http://www.gentoo.org/doc/en/2.6-koutput-user.xml
the /var/tmp/kernel-output method was a hack and never meant to be a permanent solution... I expected it to last about a week, but it's been in there for about 4 months... We're still waiting for the kernel team to get us the new modules eclass...
oh... nevermind... I was confused... I thought youu meant ${T} not the config-kernel stuff... I'll see if I can take a look at the lirc package to see how they do it because that's updated to take advantage of config-kernel...
Not sure if my error is related to this bug - so please ignore if not relevant: ---------------------------- # emerge -uDv alsa-driver Calculating dependencies ...done! >>> emerge (1 of 1) media-sound/alsa-driver-1.0.6a to / >>> md5 src_uri ;-) alsa-driver-1.0.6a.tar.bz2 >>> Unpacking source... >>> Unpacking alsa-driver-1.0.6a.tar.bz2 to /var/tmp/portage/alsa-driver-1.0.6a/work * Applying alsa-driver-1.0.5-devfix.patch... [ ok ] * Applying alsa-driver-1.0.5a-cs46xx-passthrough.patch... [ ok ] * /usr/src/linux is a symbolic link * Determining the real directory of the Linux kernel source code * Building for Linux 2.6.8-gentoo-r4 found in /usr/src/linux * A 2.5 or 2.6 kernel was detected. We are copying the kernel source tree from * //usr/src/linux-2.6.8-gentoo-r4 to /var/tmp/portage/alsa-driver-1.0.6a/temp/linux * because the alsa-driver build process overwrites files in the 2.6.x kernel tree. >>> Source unpacked. x86 ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-oss --with-kernel=/var/tmp/portage/alsa-driver-1.0.6a/temp/linux --with-isapnp=yes --with-sequencer=yes --with-cards=ens1371 configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for i686-pc-linux-gnu-gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for i686-pc-linux-gnu-ranlib... no checking for ranlib... ranlib checking for a BSD-compatible install... /bin/install -c checking how to run the C preprocessor... gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking whether time.h and sys/time.h may both be included... yes checking whether gcc needs -traditional... no checking for current directory... /var/tmp/portage/alsa-driver-1.0.6a/work/alsa-driver-1.0.6a checking cross compile... checking for directory with kernel source... /var/tmp/portage/alsa-driver-1.0.6a/temp/linux checking for kernel version... 2.6.8-gentoo-r4 checking for GCC version... Kernel compiler: gcc 3.4.1 20040803 (Gentoo Linux 3.4.1-r2, ssp-3.4-2, pie-8.7.6.5) Used compiler: gcc (GCC) 3.4.1 20040803 (Gentoo Linux 3.4.1-r2, ssp-3.4-2, pie-8.7.6.5) checking for built-in ALSA... "yes" configure: error: You have built-in ALSA in your kernel. !!! ERROR: media-sound/alsa-driver-1.0.6a failed. !!! Function econf, Line 441, Exitcode 1 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message. ---------------- This is my emerge info: # emerge info Portage 2.0.51_rc1 (default-x86-2004.0, gcc-3.4.1, glibc-2.3.4.20040808-r0, 2.6.8-gentoo-r4 i686) ================================================================= System uname: 2.6.8-gentoo-r4 i686 Pentium III (Coppermine) Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -mtune=pentium3 -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.2/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mtune=pentium3 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://mirror.nutsmaas.nl/gentoo/ ftp://ftp.gentoo.mesh-solutions.com/gentoo/ http://ftp.easynet.nl/mirror/gentoo/ ftp://ftp.easynet.nl/mirror/gentoo/ ftp://ftp.heanet.ie/pub/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo http://mir.zyrianes.net/gentoo/" MAKEOPTS="-j2" 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 alsa apm arts avi berkdb bitmap-fonts cdr crypt cscope cups emacs encode ethereal flash foomaticdb gdbm gif gpm gtk2 icc imap imlib jpeg kde ldap libg++ libwww mad mikmod mmx motif mpeg ncurses nls oggvorbis ooo-kde opengl oss pam pda pdflib perl png ppds python qt quicktime readline samba scanner sdl slang slp spell sse ssl svga tcpd tiff truetype unicode usb x86 xml2 xmms xprint xv xvid zlib linguas_en_GB linguas_el"
MickKi: | checking for built-in ALSA... "yes" | configure: error: You have built-in ALSA in your kernel. Your problem is the built-in alsa support in your kernel. You don't need to emerge alsa-driver.
Thank you tove, I've had alsa happily built-in my last few kernels. Suddenly "emerge -upDv world" drags in alsa-drivers-1.0.6 and later on 1.0.6a and wants to emerge it. "emerge -upDvt alsa-drivers" did not show anything. I did a "emerge -C alsa-drivers" it unmerged alsa-headers-1.0.6 and alsa-drivers-1.0.5a. Thereafter, I re-emerged alsa-headers (but not drivers) and that seems to have fixed it. Of course, *if* I could understand how ALSA works I wouldn't be stabbing in the dark ;-)
I patched the alsa-driver Makefile to use M= instead of SUBDIRS= and it works good now... 1.0.6a is now stable on amd64 and x86.
closing
