public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: pauln@truemesh.com
To: pauln@truemesh.com
Subject: Re: Compile problems - keymap stuff (ho, humm)
Date: Wed, 24 Apr 2002 20:06:21 +0100	[thread overview]
Message-ID: <20020424190621.GA14714@raq465.uk2net.com> (raw)
In-Reply-To: <20020424184032.GA19860@raq465.uk2net.com>

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

On Wed, Apr 24, 2002 at 07:40:32PM +0100, pauln@truemesh.com wrote:
> Dev86 0.16.0
> elks cvs
> egcs-2.91.66
> 
> Don't have time to look right now:
 
I lied :)

The mkcfg script was creating a blank Config.in, 

This seems to be as it is being clobbered by the Config.tmp file

./mkcfg auto directs to config.in

The Makefile automatically clobbers this by redirecting the output to
Config.tmp then mv'ing it into place.

I enclose a patch that strips the redirects to Config.in

Paul

[-- Attachment #2: mkcfg.patch --]
[-- Type: text/plain, Size: 988 bytes --]

Index: mkcfg
===================================================================
RCS file: /cvsroot/elks/elks/arch/i86/drivers/char/KeyMaps/mkcfg,v
retrieving revision 1.1
diff -u -r1.1 mkcfg
--- mkcfg	24 Apr 2002 17:47:04 -0000	1.1
+++ mkcfg	24 Apr 2002 19:08:51 -0000
@@ -11,7 +11,7 @@
     local CODE FILE NAME SEP='"'
 
     while read FILE CODE NAME ; do
-	printf '\t\\\n\t%-12s\tCONFIG_KEYMAP_%s' >> Config.in \
+	printf '\t\\\n\t%-12s\tCONFIG_KEYMAP_%s'  \
 		"${SEP}${NAME}" "${CODE}"
 	SEP=' '
 	printf '#include "%s"\t\t/* %s\t%-9s\t*/\n' >> keymaps.h \
@@ -20,7 +20,7 @@
 }
 
 printf '/* Automatically created - do not edit */\n\n' > keymaps.h
-printf '# Automatically created - do not edit.\n\n' > Config.in
-printf "choice 'XT Keyboard support'\t\t" >> Config.in
+printf '# Automatically created - do not edit.\n\n' 
+printf "choice 'XT Keyboard support'\t\t" 
 codes | sort +1f | process
-printf '"\t\tAmerican\n\n# EOF.\n' >> Config.in
+printf '"\t\tAmerican\n\n# EOF.\n' 

  reply	other threads:[~2002-04-24 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 18:40 Compile problems - keymap stuff (ho, humm) pauln
2002-04-24 19:06 ` pauln [this message]
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=20020424190621.GA14714@raq465.uk2net.com \
    --to=pauln@truemesh.com \
    /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