From: Andries Brouwer <aebr@win.tue.nl>
To: Rudmer van Dijk <rudmer@legolas.dynup.net>
Cc: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
Dave Jones <davej@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: build failure for 2.5.24-dj1
Date: Sun, 23 Jun 2002 14:37:55 +0200 [thread overview]
Message-ID: <20020623123755.GA18520@win.tue.nl> (raw)
In-Reply-To: <5.1.0.14.0.20020623120538.00a01160@mail.science.uva.nl>
On Sun, Jun 23, 2002 at 01:43:32PM +0200, Rudmer van Dijk wrote:
> upon inspection I found that with 'make mrproper' drivers/char/defkeymap.c
> is removed which it did not do in earlier kernels.
> on my system 'loadkeys' is not installed because i did not have the kdb
> package installed (I did not need it). looking in Documentation/Changes of
> 2.5.24-dj1 I could not find any reference to kdb so I think it should be
> added in the list of neccesary software since it is now!
>
> Rudmer
>
> +o kdb 1.06 # loadkeys --version
(i) It is a bug to regard drivers/char/defkeymap.c as a generated file.
Every now and then something is changed (sticky keys were added, etc)
and a new table can only be generated by a new loadkeys.
So, the person who makes the change changes the kernel headers in his
own tree, recompiles loadkeys against these new headers, generates
the new defkeymap.c. This new defkeymap.c is distributed as part of
the kernel source.
It will take a long time before the whole world has a new loadkeys,
so it is unreasonable to expect that everybody can generate defkeymap.c
when there have been changes.
(ii) kdb: kernel debugger; kbd: keyboard utilities.
Andries
next prev parent reply other threads:[~2002-06-23 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-23 11:43 Rudmer van Dijk
2002-06-23 12:37 ` Andries Brouwer [this message]
2002-06-23 13:59 ` Rudmer van Dijk
2002-06-23 20:16 ` Rudmer van Dijk
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=20020623123755.GA18520@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=davej@suse.de \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rudmer@legolas.dynup.net \
/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®