atkbd.c not compiling?
oliver.pinter at hardenedbsd.org
Sun Mar 1 00:36:06 UTC 2015
On Sat, Feb 28, 2015 at 11:19 PM, Garrett Cooper <yaneurabeya at gmail.com> wrote:
> On Feb 28, 2015, at 14:15, Garrett Cooper <yaneurabeya at gmail.com> wrote:
>> On Feb 28, 2015, at 13:56, Ryan Stone <rysto32 at gmail.com> wrote:
>>> On Sat, Feb 28, 2015 at 4:51 PM, Garrett Cooper <yaneurabeya at gmail.com> wrote:
>>>> I’m not sure about key_map — are you building with syscons or vt?
>>> I have no idea. I'm just running make tinderbox. So far
>>> _.sparc64.LINT, _.i386.LINT-NOINET and _.i386.LINT-VIMAGE have failed,
>>> among others.
>>> i386.LINT and sparc64.LINK have both "device sc" and "device vt" from
>>> what I can see
>> I think I figured it out. Is it because MK_VT != “no” and MK_LEGACY_CONSOLE == “no”?
> … or because MK_SYSCONS == no?
No, when you try to compile vt enabled kernel on system which running
on syscons, or the versa, then you got this problem.
Try to compile with the us.pc-ctrl or us.ctrl keyboard layout.
In bugzilla exists some patch, that fixes this issue, by altering the
font search path.
The other remaining problem is, when use try to use the VT, and it
required the kbdmux layer. The kbdmux layer then discards the custom
keyboard layout, which is configured at ukbd or atkbd level. Fix
already exists in bugzilla too.
More information about the freebsd-current