9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] Error compiling kbdfs
Date: Wed, 19 Jan 2022 23:51:06 +0100	[thread overview]
Message-ID: <3E30A9B9B784D4B22BFB2549407FBCC2@wopr.sciops.net> (raw)
In-Reply-To: <29CD2E9FA24A2B7246794DEE4FD3C84F@disroot.org>

On Wed Jan 19 23:46:46 +0100 2022, jdrm@disroot.org wrote:
> Hi again,
> 
> I've seen the previous error who creates the file latin1.h with size 0.
> 
> The error is caused when executing 
> term% mklatin.amd64 /lib/keyboard
> /lib/keyboard:1: cannot parse line
> /lib/keyboard:2: cannot parse line
> /lib/keyboard:3: cannot parse line
> /lib/keyboard:4: cannot parse line
> ...
> 
> This is my file /lib/keyboard:
> term% cat /lib/keyboard
> 	0	12         39
> 	0	13         33
> 	0	26         96
> 	0	27         43
> 	0	39        241
> 	0	41        186
> 	0	43        231
> 	0	53         45
> 	0	86         60
> 	1	3         34
> 	1	4        183
> 	1	7         38
> 	1	8         47
> 	1	9         40
> 	1	10         41
> 	1	11         61
> 	1	12         63
> 	1	13        191
> 	1	26         94
> 	1	27         42
> 	1	39        209
> 	1	40        168
> 	1	41        170
> 	1	43        199
> 	1	51         59
> 	1	52         58
> 	1	53         95
> 	1	86         62
> 	3	2        124
> 	3	3         64
> 	3	4         35
> 	3	5        126
> 	3	7        172
> 	3	26         91
> 	3	27         93
> 	3	28         10
> 	3	40        123
> 	3	41         92
> 	3	43        125
> 	3	53         47

Hi,

Where does this file come from?  If you didn't do this on purpose, you
could just revert it:

	; bind -ac /dist/plan9front /
	; git/revert /lib/keyboard

Cheers,
qwx

  reply	other threads:[~2022-01-19 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 14:50 Jacobo Da Riva
2022-01-19 17:55 ` Jacobo Da Riva
2022-01-19 22:51   ` qwx [this message]
2022-01-20 10:07     ` Jacobo Da Riva

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=3E30A9B9B784D4B22BFB2549407FBCC2@wopr.sciops.net \
    --to=qwx@sciops.net \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).