From owner-freebsd-current@FreeBSD.ORG Sun Mar 1 00:36:06 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D678C99 for ; Sun, 1 Mar 2015 00:36:06 +0000 (UTC) Received: from mail-yk0-f178.google.com (mail-yk0-f178.google.com [209.85.160.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC03A123 for ; Sun, 1 Mar 2015 00:36:05 +0000 (UTC) Received: by ykr200 with SMTP id 200so10390840ykr.12 for ; Sat, 28 Feb 2015 16:35:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9X78PZr5UsWLQdXyd4S0c952rFwv+442fY3lP9JSs3Y=; b=NWLoGwIJJo6xXvdBRD5d1T4/1G/GBA7rmjAd0PnY1en3UYBBVCZXcj70/HcdbDWKgl 9pEOMfAJNnNmDU8g1wtfSQ2I+gnU6cwjmXK3q/ZrMjywu5ZJGnT1opv9CPTK4zpkF9DW e4N9hQUO02PV6nPy2Brph2L802EDKjx6xFRqgemr4cpqMDwv8Jq3s2ji7IUKWhIMcr8S acx1W0AhPXDkFnxFZdJcn4GotJSQgOg+1ue4rQU0xoQHZduK65DK2cQajpjlEn6BaHTi fBg/OxxI4B2Esxfy0ZfOFGNMRhc89xjiYANOtakR4V9NL9mI2eVly7hNV5NDrqTSTrm/ lJFA== X-Gm-Message-State: ALoCoQlSP+DGoIEv8tKfWULbliEzbamUM+3Tl1Izs5rUn2bs7rDKmFNJN2cFzdhnukBg/Hqz9k3n MIME-Version: 1.0 X-Received: by 10.236.31.33 with SMTP id l21mr19809283yha.181.1425170158726; Sat, 28 Feb 2015 16:35:58 -0800 (PST) Received: by 10.170.56.134 with HTTP; Sat, 28 Feb 2015 16:35:58 -0800 (PST) In-Reply-To: <372ECBB0-2491-4995-8A9C-65ECF7E675AD@gmail.com> References: <2C7266F4-70C0-4AAE-876D-A03FA2E91FE4@gmail.com> <7455B5E3-EAE6-4D5D-B0DA-373F2D75397B@gmail.com> <372ECBB0-2491-4995-8A9C-65ECF7E675AD@gmail.com> Date: Sun, 1 Mar 2015 01:35:58 +0100 Message-ID: Subject: Re: atkbd.c not compiling? From: Oliver Pinter To: Garrett Cooper Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current , Ryan Stone X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2015 00:36:06 -0000 On Sat, Feb 28, 2015 at 11:19 PM, Garrett Cooper wr= ote: > On Feb 28, 2015, at 14:15, Garrett Cooper wrote: > >> On Feb 28, 2015, at 13:56, Ryan Stone wrote: >> >>> On Sat, Feb 28, 2015 at 4:51 PM, Garrett Cooper = 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.