This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: need loadkeys --mktable under cygwin
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: bertrand marquis <bertrand_marquis at yahoo dot fr>
- Cc: cygwin at cygwin dot com
- Date: Tue, 30 Mar 2004 10:42:33 -0500 (EST)
- Subject: Re: need loadkeys --mktable under cygwin
- References: <40694555.7010601@yahoo.fr>
- Reply-to: cygwin at cygwin dot com
On Tue, 30 Mar 2004, bertrand marquis wrote:
> Hello
>
> i.m trying to build the kernel under cygwin with a cross compiler
> (host=cygwin target=i386-linux) and it seems that the kernel need the
> loadkeys program to be build. I have tried to find it but it seems that
> it don't exist.
> Does anyone know a solution for that problem ?
>
> thanks
Yep. It's called "porting". :-)
Seriously, though, looking at the man page for "loadkeys", it doesn't seem
too relevant for Cygwin. In particular, the entry for "--mktable" says:
CREATE KERNEL SOURCE TABLE
If the -m (or --mktable ) option is given loadkeys prints
to the standard output a file that may be used as
/usr/src/linux/drivers/char/defkeymap.c, specifying the
default key bindings for a kernel (and does not modify the
current keymap).
Sounds like the kernel is not very cross-compilation friendly (i.e., it's
expected to be compiled *on a Linux machine*). One solution is to create
a "loadkeys" script that accepts only one option ("--mktable") and prints
out pre-defined text... Alternatively, contact the authors of the code
and notify them that their code doesn't build on Cygwin (and probably
won't on OpenBSD, either).
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/