Re: 2.5.21 make problem

[John covici <covici@ccs.covici.com>]

I had the bright idea of taking the clean out of there, so I was left
with
make dep bzImage modules_install 2>&1 |tee foo

but that didn't help -- thought it would.

on Saturday 06/15/2002 Kai Germaschewski(kai@tp1.ruhr-uni-bochum.de) wrote
 > On Sat, 15 Jun 2002, John covici wrote:
 > 
 > > Cleaning up (boot)
 > > make[2]: Entering directory `/usr/src/linux-2.5.21/arch/i386/boot/compressed'
 > > make[2]: Leaving directory `/usr/src/linux-2.5.21/arch/i386/boot/compressed'
 > > make[1]: Leaving directory `/usr/src/linux-2.5.21/arch/i386/boot'
 > > Cleaning up
 > > make[1]: Entering directory `/usr/src/linux-2.5.21/Documentation/DocBook'
 > > Cleaning up (DocBook)
 > > make[1]: Leaving directory `/usr/src/linux-2.5.21/Documentation/DocBook'
 > > make[1]: Entering directory `/usr/src/linux-2.5.21/arch/i386/boot'
 > > gcc -E  -D__BIG_KERNEL__ -traditional -DSVGA_MODE=NORMAL_VGA -DRAMDISK=512 bootsect.S -o bbootsect.s
 > > as -o bbootsect.o bbootsect.s
 > > ld -m elf_i386 -Ttext 0x0 -s --oformat binary bbootsect.o -o bbootsect
 > > make[1]: *** No rule to make target `/usr/src/linux-2.5.21/include/linux/compile.h', needed by `bsetup.s'.  Stop.
 > > make[1]: Leaving directory `/usr/src/linux-2.5.21/arch/i386/boot'
 > > make: *** [bzImage] Error 2
 > 
 > What's the command line you're using? It seems like you have "make clean" 
 > in there, no big surprise that that breaks.
 > 
 > > on Saturday 06/15/2002 Kai Germaschewski(kai@tp1.ruhr-uni-bochum.de) wrote
 > >  > On Sat, 15 Jun 2002, John covici wrote:
 > >  > 
 > >  > > make[1]: Entering directory `/usr/src/linux-2.5.21/arch/i386/boot'
 > >  > > gcc -E  -D__BIG_KERNEL__ -traditional -DSVGA_MODE=NORMAL_VGA -DRAMDISK=512 bootsect.S -o bbootsect.s
 > >  > > as -o bbootsect.o bbootsect.s
 > >  > > ld -m elf_i386 -Ttext 0x0 -s --oformat binary bbootsect.o -o bbootsect
 > >  > > make[1]: *** No rule to make target `/usr/src/linux-2.5.21/include/linux/compile.h', needed by `bsetup.s'.  Stop.
 > >  > 
 > >  > I suppose that means that compile.h does not exist at that location, for 
 > >  > whichever reason. If you do "make" (or just "make SUBDIRS=init"), it 
 > >  > should be generated. Does it output something something like "Generating 
 > >  > ../include/linux/compile.h"?
 > >  > 
 > >  > Is scripts/mkcompile_h executable?
 > 
 > You applied patches which affect the build without mentioning them. You
 > didn't answer a single question I asked. That makes it hard to help you.
 > 
 > --Kai
 > 

-- 
         John Covici
         covici@ccs.covici.com