Problems compiling kernel!
wildchild_removeme at exibis.net
Sat Jan 18 12:32:48 PST 2003
I know that I should not type the others if there is a fatal error... It
was just to see...
And it was a fresh copy of the kernel...
The problem was not with the kernel tree but with Sh-Utils binaries
which where not in /bin but in /usr/bin... anyway that's OK now and my
LFS is booting well!
Dagmar d'Surreal wrote:
> On Fri, 2003-01-17 at 22:06, WildChild wrote:
>>When I try to compile kernel I always receive a lot of error
>>make -C Documentation/DocBook clean
>>make: Entering directory `/usr/src/linux/Documentation/DocBook'
>>Makefile:188: /Rules.make: No such file or directory
>>make: *** No rule to make target `/Rules.make'. Stop.
>>make: Leaving directory `/usr/src/linux/Documentation/DocBook'
>>make: *** [clean] Error 2
>>make: /bin/pwd: Command not found
>>Hn at Hn@make: Entering directory `/usr/src/linux/arch/i386/boot'
>>make: Nothing to be done for `dep'.
>>make: Leaving directory `/usr/src/linux/arch/i386/boot'
>>scripts/mkdep -- init/*.c > .depend
>>realpath(/include) failed, No such file or directory
>>make: *** [dep-files] Error 1
>>init/main.c:383: `CONFIG_X86_L1_CACHE_SHIFT' undeclared (first use in
>>init/main.c:383: (Each undeclared identifier is reported only once
>>init/main.c:383: for each function it appears in.)
>>make: *** [init/main.o] Error 1
>>What can be the cause of these errors?
> Large chunks of your kernel source tree being missing would do it for
> the first error. The rest of the commands are ones you should not have
> typed after getting the failure for the mrproper target. Building a
> kernel is not an operation in which you should ignore fatal errors and
> just see if it works anyway... any and all fatal errors that occur
> during a kernel build WILL create a broken kernel and render your system
> relatively unbootable (pedants begone!).
> I suggest you get a copy of the latest source tarball, rm -rf
> /usr/src/linux* and then untar the fresh copy.
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-support' in the subject header of the message
More information about the lfs-support