From: pauln@truemesh.com
To: linux-8086@vger.kernel.org
Subject: Latest CVS b0rked
Date: Wed, 24 Apr 2002 08:52:41 +0100 [thread overview]
Message-ID: <20020424075240.GC16086@raq465.uk2net.com> (raw)
Change to the Makefile is looking for a script which isn't there.
I had to grab 1.62 to get to compile
make -C arch/i86/drivers/char/KeyMaps Config.in
make[1]: Entering directory
`/home/pauln/src/elks/arch/i86/drivers/char/KeyMaps'
./mkcfg > Config.tmp
/bin/sh: ./mkcfg: No such file or directory
make[1]: *** [Config.in] Error 126
revision 1.63
date: 2002/04/23 17:57:21; author: rhw2; state: Exp; lines: +6 -3
Simplified keycode system, also ANSI'fied and reindented
arch/i86/drivers/char s
ubtree.
Riley can you cvs add the file and directory then commit. This should
fix.
Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2002-04-24 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 7:52 pauln [this message]
2002-04-24 17:45 ` Latest CVS b0rked 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=20020424075240.GC16086@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