[lkml]   [2002]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: kbuild fixes and more
On Sunday 23 June 2002 22:31, Kai Germaschewski wrote:
> On Sun, 23 Jun 2002, Rudmer van Dijk wrote:
> > patched against 2.5.24-dj1 (one failed hunk) generates errors:
> > # make clean
> > <snip>
> > make -C /aicasm clean
> > make: Entering an unknown directory
> > make: *** /aicasm: No such file or directory. Stop.
> Grr, I just shouldn't do last minute changes without testing. Anyway,
> I just put a fixed version into the same place
> (patch-2.5.24-kg2.{gz,bz2}).
> (It still has some rough edges which need work, but it should at least
> get the job done)

got this error while patching (against 2.5.24 tarball):

can't find file to patch at input line 1696
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|===== BitKeeper/etc/ignore 1.21 vs 1.22 =====
|--- 1.21/BitKeeper/etc/ignore Mon Jun 17 23:06:10 2002
|+++ 1.22/BitKeeper/etc/ignore Thu Jun 20 16:11:01 2002

after removing this file from the patch it applies cleanly!
make mrproper works (no more unknown directories)
but I got this error after `make KBUILD_VERBOSE= KBUILD_MODULES=1 bzImage`:
CC drivers/char/keyboard.o
make[2]: *** No rule to make target `defkeymap.o', needed by `built-in.o'.
make[1]: *** [char] Error 2
make: *** [drivers] Error 2

so now defkeymap.c is not generated (it was removed in 2.5.24)
manually generating it works but then this happened:

CC arch/i386/boot/compressed/misc.o
make[2]: *** No rule to make target `vmlinux.scr', needed by `piggy.o'. Stop.
make[1]: *** [compressed/vmlinux] Error 2
make: *** [bzImage] Error 2

> However, I don't see why you get a failed hunk it applies cleanly against
> a bitkeeper v2.5.24 tree here. (Could you mail me the .rej file,
> privately).

I'm not using a bitkeeper tree, but the bitkeeper tree and the tarball should
be the same...

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:22    [W:0.097 / U:1.852 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site