Re: problem compiling kernels

["Jonathan D. Proulx" <jon@ai.mit.edu>]

On Sun, Jan 21, 2001 at 12:10:03PM +0000, Phillip Deackes wrote:

:I have just picked up on this thread, so excuse me if I am not answering your
:question!
:
:The Debian way of compiling the kernel is *so* easy. What I do is this:
:
:Unpack the kernel source into /usr/src
:Change the name of the dir (if necessary) to something like 'kernel-2.4.0' then
:symlink it to /usr/src/linux ('ln -s /usr/src/linux-2.4.0 /usr/src/linux'
:Cd into /usr/src/linux and do the usual 'make xconfig' as root. 
:Save the configuration.
:Enter 'make-kpkg kernel_image -revision=custom.1.0'

Wasn't originally my question, but if everyone is so set on me
learning kpkg, well it can only help me, so I have my current kernel
source 2.4.0-test10 all configured from my last build...

cd /usr/src/linux
sudo make-kpkg clean
sudo make-kpkg kernel_image  -revision=custom.1.0
     complains about arch=i386-none in many ways
sudo make-kpkg -arch=i386 -revision=custom.1.0

     and now it bombs near the end of what seems to be "make dep" with 

make[1]: i386-linux-gcc: Command not found
make[1]: *** [init/main.o] Error 127
make[1]: Leaving directory `/usr/src/linux-2.4.0-test10'
make: *** [stamp-build] Error 2

      for context the last non-error output is:

make[1]: Leaving directory `/usr/src/linux-2.4.0-test10'
test -f stamp-configure || /usr/bin/make -f
/usr/share/kernel-package/rules configure
/usr/bin/make   ARCH=i386       \
                    CROSS_COMPILE=i386-linux- bzImage
make[1]: Entering directory `/usr/src/linux-2.4.0-test10'
scripts/split-include include/linux/autoconf.h include/config
i386-linux-gcc -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing
-pipe  -march=i686   -c -o init/main.o init/main.c

Why is CROSS_COMPILE defined?  The .config builds fine with generic
make dep && make bzImage && <the rest>, I know this as this is what
I'm running.

This kpkg Version: $Revision: 1.39.2.1 $, Debian unstable, though I've
had similar trouble (not sure if it the same errors or not), over the
past 2  years or so and always just go back to vanila "make"

-Jon