My kernel version has a whitespace ("2.6.15-gentoo-r1-skas3-v9-pre8-KOZIK 1.3i). When emerging cloops : ############################### * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.15-gentoo-r1-skas3-v9-pre8-KOZIK 1.3i * Checking for suitable kernel configuration options: >>> Checking cloop_2.02-1.tar.gz's mtime... >>> WORKDIR is up-to-date, keeping... >>> Compiling source in /var/tmp/portage/cloop-2.02.1/work/cloop-2.02 ... * Preparing cloop module make: *** Brak reguł do wykonania obiektu `1.3i'. Stop. ############################### I've edited /usr/lib/portage/bin/emake to see what exactly command it runs : # make -j2 KVERSION=2.6.15-gentoo-r1-skas3-v9-pre8-KOZIK 1.3i KERNEL_DIR=/usr/src/linux all Maybe quote "" KVERSION and other ? ############################################## Portage 2.1_pre4-r1 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.5-r2, 2.6.15-gentoo-r1-skas3-v9-pre8-KOZIK1.3i i686) ================================================================= System uname: 2.6.15-gentoo-r1-skas3-v9-pre8-KOZIK1.3i i686 AMD Athlon(tm) XP 2000+ Gentoo Base System version 1.6.14 dev-lang/python: 2.4.2-r1 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O3 -march=athlon-xp -pipe -ffast-math -mfpmath=sse -ftracer -fomit-frame-pointer -fprefetch-loop-arrays" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -pipe -ffast-math -mfpmath=sse -ftracer -fomit-frame-pointer -fprefetch-loop-arrays" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.prz.rzeszow.pl http://gentoo.zie.pg.gda.pl http://gentoo.po.opole.pl ftp://gentoo.po.opole.pl" LANG="pl_PL.ISO-8859-2" LC_ALL="pl_PL.ISO-8859-2" LINGUAS="pl" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X acpi alsa apache2 avi berkdb bitmap-fonts cdr cli crypt ctype cups dba dbus dri emboss encode esd expat fastbuild foomaticdb force-cgi-redirect fortran ftp gd gdbm gif gnome gpm gtk gtk2 hal imlib isdnlog jpeg libg++ libwww mad memlimit mikmod mmx mmxext motif mp3 mpeg ncurses nls nptl ogg opengl pam pcre pdflib perl png posix pppd python quicktime readline sdl session simplexml soap sockets spell spl sse ssl tcpd tokenizer truetype truetype-fonts type1-fonts udev vorbis xml xmms xsl xv zlib elibc_glibc kernel_linux linguas_pl userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LDFLAGS, PORTDIR_OVERLAY
ignoring the fact that using spaces in the kernel version is dumb, this is a bug in the kernel eclasses, not emake
This is actually an ebuild bug. As such I have left open and cc'd the maintainer in to make comments. Taken from cloop: BUILD_PARAMS="KVERSION=${KV_FULL} KERNEL_DIR=${KV_DIR}" As you can see it doesn't quote the KV_FULL which is passed to emake. Regardless, concensus is still not to use spaces in the version string. It will break several things outside of the scope of this bug. I would strongly recommend s: :_:g across all localversions* or whatever it is your using to pass the version string with spaces. Also, we cannot support kernels which we dont distribute.
We have decided that supporting versions with spaces in, isn't going to be possible at present. Please could you test again, using versioning which doesnt contain a space. Regards, John
I have already removed space and everything works fine.
*** Bug 146576 has been marked as a duplicate of this bug. ***
*** Bug 131292 has been marked as a duplicate of this bug. ***