From: "Marc-F. LUCCA-DANIAU" <mfld.fr@gmail.com>
To: Juan Perez-Sanchez <lithoxs@gmail.com>
Cc: ELKS <Linux-8086@vger.kernel.org>
Subject: Re: Build failed on latest ELKS
Date: Wed, 18 May 2016 21:37:27 +0200 [thread overview]
Message-ID: <573CC477.1020308@gmail.com> (raw)
In-Reply-To: <CAD6VGubPLeGzKL0V0wSSeKOC23CSTwXsLLRsagaZNq4Bbd++5A@mail.gmail.com>
Hello Juan,
Thanks for pointing the previous report.
I guess you meant ""grep" does not like it", and octal as "0xxx" in C
files, not "\xxx" as in shell.
Adding option -a to grep gives a correct Config.in, but one thing stills
not clear for me:
do you know what is the code page that is supposed to be used to encode
the characters in the keys-*.h ?
In the IBM PS/2 BIOS TechRef, I see no clue about this encoding, just a
Keycode / ASCII table with US keyboard layout.
MFLD
Le 17/05/2016 22:15, Juan Perez-Sanchez a écrit :
> Hello,
>
> This problem (with possible workaround) was reported in:
>
> http://www.spinics.net/lists/linux-8086/msg00675.html
>
> The problem is that keymap tables use "extended ascii" characters,
> this is, codes greater than 127, and current "make" don't like it. For
> example, accented a is written as 'á' and should be written as'\341'.
>
> This include files are C code and should use plain ascii. However,
> this is a lot of work.
>
> Juan
>
>
> On Tue, May 17, 2016 at 7:37 AM, Marc-F. LUCCA-DANIAU <mfld.fr@gmail.com> wrote:
>> Hello,
>>
>> I just took the latest version of ELKS from Jody's GIT master branch, and I
>> got an issue while building ELKS.
>> I am using the "build.sh" script for the newbie I am :-)
>>
>>
>> With default configuration, build fails because the following file is
>> malformed:
>> /home/mfld/advantech/elks/elks/arch/i86/drivers/char/KeyMaps/keymaps.h:
>> /* Automatically created - do not edit */
>>
>> #include "Fichier" /* binaire keys-be.h correspondant */
>> #include "Fichier" /* binaire keys-de.h correspondant */
>> #include "Fichier" /* binaire keys-es.h correspondant */
>> #include "Fichier" /* binaire keys-it.h correspondant */
>> #include "Fichier" /* binaire keys-se.h correspondant */
>> #include "Fichier" /* binaire keys-uk.h correspondant */
>> #include "keys-dv.h" /* DV Dvorak */
>> #include "keys-us.h" /* US American */
>>
>> (I am using a Gentoo configured in French, so the french strings)
>>
>>
>> This file came from the malformed Config.in:
>> # Automatically created - do not edit.
>>
>> choice 'XT Keyboard support' \
>> "keys-be.h correspondant CONFIG_KEYMAP_binaire \
>> keys-de.h correspondant CONFIG_KEYMAP_binaire \
>> keys-es.h correspondant CONFIG_KEYMAP_binaire \
>> keys-it.h correspondant CONFIG_KEYMAP_binaire \
>> keys-se.h correspondant CONFIG_KEYMAP_binaire \
>> keys-uk.h correspondant CONFIG_KEYMAP_binaire \
>> Dvorak CONFIG_KEYMAP_DV \
>> American CONFIG_KEYMAP_US" American
>>
>> # EOF.
>>
>>
>> Error went away after changing the kernel configuration:
>> Select console driver: from <Direct> to <BIOS>
>>
>>
>> I am not at ease with the Config.in generation, any idea here ?
>>
>> MFLD
>>
>> --
>> 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
--
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 prev parent reply other threads:[~2016-05-18 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 12:37 Build failed on latest ELKS Marc-F. LUCCA-DANIAU
2016-05-17 20:15 ` Juan Perez-Sanchez
2016-05-18 19:37 ` Marc-F. LUCCA-DANIAU [this message]
2016-05-18 20:27 ` Juan Perez-Sanchez
2016-05-19 8:44 ` Marc-François LUCCA-DANIAU
2016-05-20 0:53 ` Juan Perez-Sanchez
2016-05-20 1:34 ` Jody Bruchon
2016-05-20 12:23 ` Marc-F. LUCCA-DANIAU
2016-05-20 17:52 ` Juan Perez-Sanchez
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=573CC477.1020308@gmail.com \
--to=mfld.fr@gmail.com \
--cc=Linux-8086@vger.kernel.org \
--cc=lithoxs@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.