From: pauln@truemesh.com
To: linux-8086@vger.kernel.org
Subject: Compile problems - keymap stuff (ho, humm)
Date: Wed, 24 Apr 2002 19:40:32 +0100 [thread overview]
Message-ID: <20020424184032.GA19860@raq465.uk2net.com> (raw)
Dev86 0.16.0
elks cvs
egcs-2.91.66
Don't have time to look right now:
Basic config with GENERIC_DISK removed.
make[3]: Entering directory `/home/pauln/src/elks/arch/i86/drivers/char'
bcc -0 -i -O -I/home/pauln/src/elks/include -DELKS_VERSION_CODE=0x0000FF04 -DUTS_RELEASE=\"0.1.0-pre4\" -D__KERNEL__ -ansi -c -o xt_key.o xt_key.c
xt_key.c:157.22: error: xtkb_scan_caps undeclared
xt_key.c:157.27: error: illegal indirection
xt_key.c:159.25: error: xtkb_scan_shifted undeclared
xt_key.c:159.30: error: illegal indirection
xt_key.c:164.26: error: xtkb_scan_ctrl_alt undeclared
xt_key.c:164.31: error: illegal indirection
xt_key.c:171.31: error: illegal indirection
xt_key.c:174.17: error: xtkb_scan undeclared
xt_key.c:174.22: error: illegal indirection
xt_key.c:177.30: error: illegal indirection
xt_key.c:179.30: error: illegal indirection
make[3]: *** [xt_key.o] Error 1
make[3]: Leaving directory `/home/pauln/src/elks/arch/i86/drivers/char'
make[2]: *** [drivers/char/chr_drv.a] Error 2
make[2]: Leaving directory `/home/pauln/src/elks/arch/i86'
make[1]: *** [Image] Error 2
make[1]: Leaving directory `/home/pauln/src/elks'
make: *** [elks] Error 2
Seems to be the KeyMap stuff:
find . -type f -exec grep -l xtkb_scan \{\} \;
./arch/i86/drivers/char/KeyMaps/keys-be.h
./arch/i86/drivers/char/KeyMaps/keys-de.h
./arch/i86/drivers/char/KeyMaps/keys-dv.h
./arch/i86/drivers/char/KeyMaps/keys-es.h
./arch/i86/drivers/char/KeyMaps/keys-fr.h
./arch/i86/drivers/char/KeyMaps/keys-se.h
./arch/i86/drivers/char/KeyMaps/keys-uk.h
./arch/i86/drivers/char/KeyMaps/keys-us.h
./arch/i86/drivers/char/xt_key.c
Paul
next reply other threads:[~2002-04-24 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 18:40 pauln [this message]
2002-04-24 19:06 ` Compile problems - keymap stuff (ho, humm) pauln
2002-04-24 19:12 ` pauln
2002-04-24 21:51 ` Riley Williams
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=20020424184032.GA19860@raq465.uk2net.com \
--to=pauln@truemesh.com \
--cc=linux-8086@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