Date: Fri, 13 Jul 2018 11:15:22 +0100 From: tech-lists <tech-lists@zyxst.net> To: Dimitry Andric <dim@FreeBSD.org>, Mark Millard <marklmi@yahoo.com> Cc: 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: <b7ec00a7-f30e-b0a6-bc7b-191e7d6ae367@zyxst.net> In-Reply-To: <6DDED0A0-588D-4323-8E22-1267AA06615E@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b7ec00a7-f30e-b0a6-bc7b-191e7d6ae367>