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: Mon, 24 Jun 2002 19:59:05 +0200 [thread overview]
Message-ID: <20020624175547Z314596-22020+10086@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0206231913170.24916-100000@chaos.physics.uiowa.edu>
On Monday 24 June 2002 02:15, Kai Germaschewski wrote:
> On Sun, 23 Jun 2002, Rudmer van Dijk wrote:
> > got this error while patching (against 2.5.24 tarball):
>
> Hmmh, it seems all three errors you get are related to the same problem: I
> don't know the proper command how to create a gnu patch from my bk tree.
>
> Anyway, so now there's a version 3 which I diffed manually. Still has the
> warning for "make clean", but should work.
Did not see this warning, it applies cleanly 8-)
>
> (I couldn't help but wonder: Is three tries enough to get it right?)
It looks like it, it compiles in one go! (did not run it (yet))
I was only wondering about this:
# make KBUILD_VERBOSE= KBUILD_MODULES=1 bzImage
<snip>
CP drivers/char/defkeymap.c
<snip>
LD drivers/char/built-in.o
rm defkeymap.c
^^^^^^^^^
<snip>
why is it first copied to this dir and later on, after linking all char
drivers together, it is removed again... isn't it simpler to just leave the
file in place??
I also like the complete silence of the final linking:
BUILD arch/i386/boot/bzImage
Root device is (3, 2)
Boot sector 512 bytes.
Setup is 2636 bytes.
System is 847 kB
This is very nice!
I have a minor 'fix' included
Rudmer
--- linux-2.5.24-kg3/Makefile.orig 2002-06-24 19:48:48.000000000 +0200
+++ linux-2.5.24-kg3/Makefile 2002-06-24 19:49:01.000000000 +0200
@@ -5,7 +5,7 @@
# *DOCUMENTATION*
# Too see a list of typical targets execute "make help"
-# More info can be located in ./Documentation/kbuild
+# More info can be found in ./Documentation/kbuild
# Comments in this file is targeted only to the developer, do not
# expect to learn how to build the kernel reading this file.
-or-
--- linux-2.5.24-kg3/Makefile.orig 2002-06-24 19:48:48.000000000 +0200
+++ linux-2.5.24-kg3/Makefile 2002-06-24 19:49:01.000000000 +0200
@@ -5,7 +5,7 @@
# *DOCUMENTATION*
# Too see a list of typical targets execute "make help"
-# More info can be located in ./Documentation/kbuild
+# More info is located in ./Documentation/kbuild
# Comments in this file is targeted only to the developer, do not
# expect to learn how to build the kernel reading this file.
next prev parent reply other threads:[~2002-06-24 17:55 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
2002-06-24 0:15 ` Kai Germaschewski
2002-06-24 17:59 ` Rudmer van Dijk [this message]
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=20020624175547Z314596-22020+10086@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®