Date: Fri, 13 Jul 2018 08:27:10 -0700 From: Mark Millard <marklmi@yahoo.com> To: tech-lists <tech-lists@zyxst.net> Cc: Dimitry Andric <dim@FreeBSD.org>, freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org> Subject: Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3 Message-ID: <43C85CB9-2F8A-4DB2-85F3-CAE6371666E4@yahoo.com> In-Reply-To: <b7ec00a7-f30e-b0a6-bc7b-191e7d6ae367@zyxst.net> References: <A7BBACBB-44A1-4F95-B4F6-498B72238FC5@yahoo.com> <a8cc68ec-e87d-9133-7ad9-59c5b42ed749@zyxst.net> <2F72F7DB-F5DD-471A-B644-9CDE3FABFAC1@yahoo.com> <6DDED0A0-588D-4323-8E22-1267AA06615E@FreeBSD.org> <b7ec00a7-f30e-b0a6-bc7b-191e7d6ae367@zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-Jul-13, at 3:15 AM, tech-lists <tech-lists at zyxst.net> wrote: > On 12/07/2018 19:32, Dimitry Andric wrote: >> No, it's because sys/crypto/armv8/armv8_crypto_wrap.c includes >> <arm_neon.h>, an intrinsics header, which in turn requires = <stdint.h>. >> 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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43C85CB9-2F8A-4DB2-85F3-CAE6371666E4>