From: Felix Janda <felix.janda@posteo.de>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] unicode option for not working correctly since commit: bad17ea03
Date: Tue, 20 Sep 2016 15:33:41 -0400 [thread overview]
Message-ID: <20160920193341.GA309@nyan> (raw)
In-Reply-To: <d1b13e17-a967-8e5e-e8d2-aa1984b35859@ziu.info>
Michal Soltys wrote:
> On 2016-09-20 01:58, Felix Janda wrote:
> > 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)?
> >
>
> The last commit that did compile (where it was working fine) was:
>
> http://git.kernel.org/cgit/linux/kernel/git/legion/kbd.git/commit/?id=8d37c0e76fdb487845da74bdf0bbce13eebf7596
>
> (so directly preceeding the one you mentioned)
>
> And since:
>
> http://git.kernel.org/cgit/linux/kernel/git/legion/kbd.git/commit/?id=bad17ea033bf571e03b05e1330e81e6238fd61f0
>
> loadkeys -u have issues
I understand that.
It would just be nice to see more clearly which of the two commits
causes the issue. (I think the compilation failure is unrelated to your
issue.)
So, with the broken commit, does only the compilation of dumpkeys fail
or also something else? If only dumpkeys fails, it should be no problem
to build loadkeys, and you could test if already that commit breaks
loadkeys.
Felix
next prev parent reply other threads:[~2016-09-20 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 1:06 [kbd] unicode option for not working correctly since commit: bad17ea03 Michal Soltys
2016-09-06 19:26 ` Alexey Gladkov
2016-09-19 20:10 ` Michal Soltys
2016-09-19 23:58 ` Felix Janda
2016-09-20 18:13 ` Michal Soltys
2016-09-20 19:33 ` Felix Janda [this message]
2016-09-21 9:53 ` Alexey Gladkov
2016-10-19 19:36 ` Alexey Gladkov
2016-10-19 21:36 ` Michal Soltys
2016-10-31 15:28 ` Michal Soltys
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=20160920193341.GA309@nyan \
--to=felix.janda@posteo.de \
--cc=kbd@lists.altlinux.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 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.