From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on sa.local.altlinux.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 Date: Mon, 19 Sep 2016 19:58:01 -0400 From: Felix Janda To: Linux console tools development discussion Message-ID: <20160919235801.GA412@nyan> References: <10c42442-39d5-a138-b2b6-902c70296d89@ziu.info> <20160906192614.GH31992@comp-core-i7-2640m-0182e6.fortress> <32bb3467-ff33-c1d3-ce94-878f891d2c9c@ziu.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32bb3467-ff33-c1d3-ce94-878f891d2c9c@ziu.info> User-Agent: Mutt/1.6.1 (2016-04-27) Subject: Re: [kbd] unicode option for not working correctly since commit: bad17ea03 X-BeenThere: kbd@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Linux console tools development discussion List-Id: Linux console tools development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 00:00:19 -0000 Archived-At: List-Archive: Michal Soltys wrote: [..] > On pre-2.0 versions all will be working fine (or to be precise, > pre-commit I bisected). After that commit some will be failing. If you > do setfont -m 8859-2 - this will provide the workaround. It might be useful to further bisect: I can see that compilation of dumpkeys will fail directly after commit http://git.kernel.org/cgit/linux/kernel/git/legion/kbd.git/commit/?id=3fdbff332a6ef88a2447584c47a8616dceb19548 (e.g. because of missing lk_list_charsets). But is it in this situation maybe still possible to directly build loadkeys ("make loadkeys" in the src directory)? Felix