From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Marc-F. LUCCA-DANIAU" Subject: Re: Build failed on latest ELKS Date: Wed, 18 May 2016 21:37:27 +0200 Message-ID: <573CC477.1020308@gmail.com> References: <573B1085.2040806@gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=2edNsl6d0wER1xc/9pKsA/yfYDGbHbUfIAU9h5bab6g=; b=CWifAhtoDQjUhNN8ATPv7Sy6f9oJej6rCqlsWdh66A9axAagtfee4ARhsLSHrMb9RX /qvU7YcUPoith824sGLfVaDgW5dx3EUNSX5IO/M6N6N2nko1ffpsT6liMzhlJOd3zNk1 /EwuTtr9WVLr+KhBT4j+3dLAaqBZOY+A3ThsnwkHtitINFPpbnpOhsQ3isbLCdWir43X VlRu8t7+ywUAASV9G4qSHmlQGhZf6Dh2u9XAmfiYKFs6g9Udfqp2YPvwXmsV4mG+kpE9 ufNg2EAWaZU8SAOtpKy3D9pLS/AHbv1Q4VwV/uXiIB0tMMAKnU79NSelIBhFsQ7fnqjE rizQ== In-Reply-To: Sender: linux-8086-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="utf-8"; format="flowed" To: Juan Perez-Sanchez Cc: ELKS Hello Juan, Thanks for pointing the previous report. I guess you meant ""grep" does not like it", and octal as "0xxx" in C=20 files, not "\xxx" as in shell. Adding option -a to grep gives a correct Config.in, but one thing still= s=20 not clear for me: do you know what is the code page that is supposed to be used to encode= =20 the characters in the keys-*.h ? In the IBM PS/2 BIOS TechRef, I see no clue about this encoding, just a= =20 Keycode / ASCII table with US keyboard layout. MFLD Le 17/05/2016 22:15, Juan Perez-Sanchez a =C3=A9crit : > 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. Fo= r > example, accented a is written as '=C3=A1' 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 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 i= s >> malformed: >> /home/mfld/advantech/elks/elks/arch/i86/drivers/char/KeyMaps/keymaps= =2Eh: >> /* 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 to >> >> >> 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" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html