From: Rudmer van Dijk <rvandijk@science.uva.nl>
To: Kai Germaschewski <kai-germaschewski@uiowa.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild fixes and more
Date: Sun, 23 Jun 2002 23:02:54 +0200 [thread overview]
Message-ID: <20020623205939Z317140-22020+9329@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0206231527030.6241-100000@chaos.physics.uiowa.edu>
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`:
<snip>
CC drivers/char/keyboard.o
make[2]: *** No rule to make target `defkeymap.o', needed by `built-in.o'.
Stop.
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:
<snip>
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...
Rudmer
next prev parent reply other threads:[~2002-06-23 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200206232013.g5NKDjf189958@moon.its.uiowa.edu>
2002-06-23 20:31 ` Kai Germaschewski
2002-06-23 21:02 ` Rudmer van Dijk [this message]
2002-06-24 0:15 ` Kai Germaschewski
2002-06-24 17:59 ` Rudmer van Dijk
2002-06-23 18:39 Kai Germaschewski
2002-06-23 20:11 ` Rudmer van Dijk
2002-06-23 20:16 ` Rudmer van Dijk
2002-06-23 23:19 ` Petko Manolov
2002-06-23 22:05 ` Sam Ravnborg
2002-06-24 1:22 ` Kai Germaschewski
2002-06-24 6:21 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020623205939Z317140-22020+9329@vger.kernel.org \
--to=rvandijk@science.uva.nl \
--cc=kai-germaschewski@uiowa.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®