From owner-freebsd-current@freebsd.org Thu Jul 12 09:44:11 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 9FB4010479BC; Thu, 12 Jul 2018 09:44:11 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (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 3886B867A8; Thu, 12 Jul 2018 09:44:11 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id DEA442FF; Thu, 12 Jul 2018 05:44:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 12 Jul 2018 05:44:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= 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=EMaXimHYrrdwjfoLDZYA2Mh9PsoDZ fqkBUQyA1Xm27g=; b=BpHBge6vwlsNpJToPgMayqyEEJJOv4vZiV1AT3iRJiFO8 i9UqhltNg7ZkL53dXwYqdpohQA5ueRPYT+XjO8nU+4Oc9Iyh1gqmI7ome6m//uJx cQiSkvrSR673IImoqPH2sqv8ER03ailK2F0lk08/7yiZ5BEfrEiF+JYvjmlJ1Uvd R75uoOseWu9Khz7HWOLa03xxtZu9MdIL5/6kXlj+MauXay09AmM6UcYqDEKAzbZc kdlgz6WLLQ3cMMZYatK6Mk55hqJh53AjxED789u5Y9cA5Nj77o5oKB1UZ++/82sr GaVDulsoVvBQAmq4hSXygFjF+0krG449OY7syrn+w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=EMaXim HYrrdwjfoLDZYA2Mh9PsoDZfqkBUQyA1Xm27g=; b=M2EAaGPZ1sYNbvnFjuTRjD 9q5qpHm1TjmqOsv0tp/dyO6T2Y05da1V1a4KvCsdzBTROoqSOLDCdkrFkDFxD+MN RrFJLwXV4c2cz6JzBZzRRlpslYkXRCC0I+3b1LAKO15zcNYv0o2ayJF2J7A4Xca5 NfTdP+mU8IfYQKJ23jsbuNwXh8ds2DDP3/siroPdw/Bt+R8EhuMsSLvXE/sF29jS TaGjY8bdvgiOlimbq/02g0zbVyLdkJlgExdWWcCDI1d9sLQfpQ8ekaPhN72CmQ/r TwljdAPkleiEuGb0feoNrJLkDERWvLNCP/s5EYD3acNDm86ZjlKdF72IVCLkoKLA == 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 56A871026B; Thu, 12 Jul 2018 05:44:01 -0400 (EDT) Subject: Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3 To: Mark Millard , FreeBSD Current , freebsd-arm , FreeBSD Toolchain References: From: tech-lists Organization: none Message-ID: Date: Thu, 12 Jul 2018 10:44:00 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; 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: Thu, 12 Jul 2018 09:44:11 -0000 On 11/07/2018 17:21, Mark Millard wrote: > It seems from the quoted material that neither kernel-toolchain nor > build world was done before buildkernel . My understanding is that > the intent is that one or the other be done first. (But for aarch64 > currently only buildworld works.) Thanks for this. I'm running a buildworld now. For how long has it been the case that buildworld is needed for buildkernel? Coming from amd64 and before that, i386, in situations where I've only wanted to install a custom kernel, I was firstly used to making and installing it from /sys/{i386,amd64}/conf. Then that broke a number of years ago. Then got used to making kernel in /usr/src with make buildkernel && make installkernel. And now this is broken, on aarch64-arm64. Nobody knows if it's accidental or policy. -- J.