From owner-freebsd-current@freebsd.org Fri Jul 13 15:27:21 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 BC2511040895 for ; Fri, 13 Jul 2018 15:27:21 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-14.consmr.mail.bf2.yahoo.com (sonic310-14.consmr.mail.bf2.yahoo.com [74.6.135.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DE4738B16E for ; Fri, 13 Jul 2018 15:27:20 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: unhdnzIVM1kWBto7x6j6I96FGZ.etS60DFg4U3OTBLiyk4Q7rYcUlxDkykJe1dM iNM5PL9MaacU90ETusGM_3hEP9bZr6KZvQNffxnpkpUxsAXaQPROyQv4Sg5.Lo5Q1bp.H91xq25R i3tb_eiidhIVBsjhmDJJuYywJISahG9zIWQizmhz7EPCPYB0LwP1pT9Ij_8xjkIfsR0sU7mnDdP2 KmqtN9FDUIWD_9GXdBviJLne56XJZ5f77Vmldp.q38mx69J3CeGGR8hwSHdmRS0hUCtLfr9.qYUI 9BDUy4Bu8MkeMOFTMTkf1WoOgV0Pe_tJK0UL4C6vWirbak9SFJb_kakRuI6C8RKHdGR364H7l.6p zb4N.lUdyeme3RMVHHkRjMeNob2YY643DiH3l70RC.i6Otik1D2QQrmPP4JSB0DzrHixjth0LlSs kjW776_NrTQ.QFI.hzlVAS2iSbuj9XbLAyJrv4wCraadYmJ6aSr6tJVHeFGe.V.DohpOGwnfvKxk Df5.rcUFxavVeYlEKN_9aZi7_jBYcXRU5LJ5RwkjcQ1KI_3HhKVmBYL8eOenyVsFUD7Icq7YMM9W 0NSs2T8J5Yjon4EMiSIIxv_vWeaFMKC3_LZ34c.DS_nS9YXTEMHPWN6FJ1q9XqCbgURIX4P158rL um69AkVAkEsyw5lGdIbzuakBZwXRllJguCn1FVwEQaF7G34WxpIoJDhHuD8dBkZSzTfaBWKfhRJ3 1rygbxDnGi8RmQitqjud.ObdEarDYaQCsmKLkILn.E6.DS2leG3WO5XT.8c7LZcChXAbbwjWPT4j 7Zfbt5aZbz_CMZkKvyUEUulhMMcrVc8L_wyojOcUxfuYiMmvXee28vU9EdGp1pLNY.PEIZ7blebL TkYlQN6pOXYo7sxu_qxjqXHUKtfRiforw2b543yp5UwOFRWSvMLNg4nMG0.iU6rhFzd0Mje2CqkE tdSMIaMHLexPH0kD12hosgNinexwv08eTyuS9WW4PncrMNXp0tiKNj0qpp75d5Vka.3zkkg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.bf2.yahoo.com with HTTP; Fri, 13 Jul 2018 15:27:14 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp404.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 397c607cf7ff4eb30e9b1315c185d34f; Fri, 13 Jul 2018 15:27:12 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3 From: Mark Millard In-Reply-To: Date: Fri, 13 Jul 2018 08:27:10 -0700 Cc: Dimitry Andric , freebsd-arm , FreeBSD Current , FreeBSD Toolchain Content-Transfer-Encoding: quoted-printable Message-Id: <43C85CB9-2F8A-4DB2-85F3-CAE6371666E4@yahoo.com> References: <2F72F7DB-F5DD-471A-B644-9CDE3FABFAC1@yahoo.com> <6DDED0A0-588D-4323-8E22-1267AA06615E@FreeBSD.org> To: tech-lists X-Mailer: Apple Mail (2.3445.9.1) 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 15:27:22 -0000 On 2018-Jul-13, at 3:15 AM, tech-lists wrote: > 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. >=20 > Hi, >=20 > Ok, it's finished building and installing. The command I used was = this: >=20 > # make -j10 buildworld && make -j10 buildkernel KERNCONF=3DRPI3 make -j10 buildworld buildkernel KERNCONF=3DRPI3 would have worked. > and it all built, (so I'll close the PR I opened). Then I did make = installkernel KERNCONF=3DRPI3 and because I thought might as well = install everything now it's built, mergemaster -p and make installworld = && mergemaster -Ui. >=20 > 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? If you first clear out the old build, then such would be true. (Where, for targeting aarch64, kernel-toolchain needs to be avoided.) But you can buildkernel using the results of the existing buildworld (or kernel-toolchain if it applies) when it is okay to not clear out the old build first. (kernel developers doing kernel development likely do this a lot.) Another way to make tradeoffs is to use META_MODE so that partial rebuilds are done, avoiding some of the strictly unnecessary rebuild activity. This would involve buildworld or kernel-toolchain (as appropriate for the target architecture). =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)