Date: Sun, 1 Mar 2015 01:35:58 +0100 From: Oliver Pinter <oliver.pinter@hardenedbsd.org> To: Garrett Cooper <yaneurabeya@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Ryan Stone <rysto32@gmail.com> Subject: Re: atkbd.c not compiling? Message-ID: <CAPQ4fftqRsjX-_sJANmZXq-tHX3dRtWo12p%2BTSuKL41U-PxjJw@mail.gmail.com> In-Reply-To: <372ECBB0-2491-4995-8A9C-65ECF7E675AD@gmail.com> References: <CAFMmRNznx5fBxfhhTY8menNNqCBaPR9w6-VS9as22WEqsTHLkw@mail.gmail.com> <2C7266F4-70C0-4AAE-876D-A03FA2E91FE4@gmail.com> <CAFMmRNx1nxnirAXbLTzTWwZf=7stVpfwwcbyqvsz619xE1Ax8g@mail.gmail.com> <7455B5E3-EAE6-4D5D-B0DA-373F2D75397B@gmail.com> <372ECBB0-2491-4995-8A9C-65ECF7E675AD@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 28, 2015 at 11:19 PM, Garrett Cooper <yaneurabeya@gmail.com> wr= ote: > On Feb 28, 2015, at 14:15, Garrett Cooper <yaneurabeya@gmail.com> wrote: > >> On Feb 28, 2015, at 13:56, Ryan Stone <rysto32@gmail.com> wrote: >> >>> On Sat, Feb 28, 2015 at 4:51 PM, Garrett Cooper <yaneurabeya@gmail.com>= wrote: >>>> I=E2=80=99m not sure about key_map =E2=80=94 are you building with sys= cons 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 !=3D =E2=80=9Cno=E2=80=9D = and MK_LEGACY_CONSOLE =3D=3D =E2=80=9Cno=E2=80=9D? > > =E2=80=A6 or because MK_SYSCONS =3D=3D 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPQ4fftqRsjX-_sJANmZXq-tHX3dRtWo12p%2BTSuKL41U-PxjJw>