From owner-freebsd-current@freebsd.org Fri Jul 13 10:15:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6E21103244C; Fri, 13 Jul 2018 10:15:31 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 797D57E795; Fri, 13 Jul 2018 10:15:31 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 14A6D21FE5; Fri, 13 Jul 2018 06:15:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 13 Jul 2018 06:15:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=OippaRKapkCahOpgibX+QMrsj8rux X9DVzhDXdn4DBk=; b=CcIyeix5WyR1WXWVNWAJzgUSkbRMm7yiZraEuf/XiOmF9 FjoFw6fpb7kdFT1ITZeysTat4NmBozMgb0QqQi/Pk1OTrZILlvs23jsFa4hwQ6m0 SObHe4Q/2WRxEnKl1oCZh5f1N27kT1pV/QSiWzUIF/wjH3ldg621KnjKbcJVvDsy JBGqlRz5K29kK75JGUj4aBYVpHs86uQBHQiDQHg0C8DN95qfOUzQSmQWawOThpoo aFw+ntWkVpMS43HBiYMSn2spX4D0ryepuv60lx5xuRRXEYusp04aK6Z0szKPMtvK 19WFVXaZT8Yr8Y+2GR1RA1j8HYQnCKHIL9R65X37g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=OippaR KapkCahOpgibX+QMrsj8ruxX9DVzhDXdn4DBk=; b=HEv9AfKGy/2e/wguTFT+ZH +5lhtWKD+Y5JnMBBDz3Pnr0uorXnCxxAuroUq6XIxLyZrnLKQh6owWdC2oEVx0lw KmkZ65TQjTzTo48oxs1P8llBLYcVESbfzrzk8oDFLzEqRki62KHHZ4Q2MEDwQBeS eeflVOGNfp+Akzb7Eh8JJ5uhinlf0ZuGjIje+gJClvFgkvGtQdm+jk2N+5UgJ+4g eO68QmDef7xZX6fTsKnCDcNNoP0NhKr6xYZkuAqeP1TEcLax4TWLtMYTYiSkM7Be eTTR8zVsYuRxYIowEllOCZNNel9nbijp1vK7L6L+QxERiYbQO1yRRIImndpSH2Nw == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id E7F13E4636; Fri, 13 Jul 2018 06:15:23 -0400 (EDT) Subject: Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3 To: Dimitry Andric , Mark Millard Cc: freebsd-arm , FreeBSD Current , FreeBSD Toolchain References: <2F72F7DB-F5DD-471A-B644-9CDE3FABFAC1@yahoo.com> <6DDED0A0-588D-4323-8E22-1267AA06615E@FreeBSD.org> From: tech-lists Organization: none Message-ID: Date: Fri, 13 Jul 2018 11:15:22 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <6DDED0A0-588D-4323-8E22-1267AA06615E@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 13 Jul 2018 10:15:32 -0000 On 12/07/2018 19:32, Dimitry Andric wrote: > No, it's because sys/crypto/armv8/armv8_crypto_wrap.c includes > , an intrinsics header, which in turn requires . > > This was introduced inhttps://svnweb.freebsd.org/changeset/base/308921, > and at the time resulted in similar build failures, specifically when > one attempted to build a new kernel, without building world or a new > toolchain first. Hi, Ok, it's finished building and installing. The command I used was this: # make -j10 buildworld && make -j10 buildkernel KERNCONF=RPI3 and it all built, (so I'll close the PR I opened). Then I did make installkernel KERNCONF=RPI3 and because I thought might as well install everything now it's built, mergemaster -p and make installworld && mergemaster -Ui. So I take it then, that every time I want to build a kernel, I either have to do the above or use make kernel-toolchain. Is this correct? thanks, -- J.