Date: Thu, 12 Jul 2018 20:32:30 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Mark Millard <marklmi@yahoo.com> Cc: tech-lists <tech-lists@zyxst.net>, 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: <6DDED0A0-588D-4323-8E22-1267AA06615E@FreeBSD.org> In-Reply-To: <2F72F7DB-F5DD-471A-B644-9CDE3FABFAC1@yahoo.com> References: <A7BBACBB-44A1-4F95-B4F6-498B72238FC5@yahoo.com> <a8cc68ec-e87d-9133-7ad9-59c5b42ed749@zyxst.net> <2F72F7DB-F5DD-471A-B644-9CDE3FABFAC1@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_538A729A-DF98-48DA-807D-508A89EBF62C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
On 12 Jul 2018, at 15:23, Mark Millard via freebsd-toolchain =
<freebsd-toolchain@freebsd.org> wrote:
>=20
> On 2018-Jul-12, at 2:44 AM, tech-lists <tech-lists at zyxst.net> =
wrote:
>=20
>> 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.)
>>=20
>> Thanks for this. I'm running a buildworld now.
>>=20
>> 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.
>=20
> It has been true since clang added use of stdint.h to the kernel =
build.
> Prior to this stdint.h was not needed to build the kernel for any
> architecture (as far as I know).
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 in https://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.
-Dimitry
--Apple-Mail=_538A729A-DF98-48DA-807D-508A89EBF62C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.2
iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCW0eevgAKCRCwXqMKLiCW
o2PxAKDD0fu/b9FzE0adQQw7NOoggolVPgCfWlY233kbNrNJXnvnQCIFOD4OAhY=
=e9Ml
-----END PGP SIGNATURE-----
--Apple-Mail=_538A729A-DF98-48DA-807D-508A89EBF62C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6DDED0A0-588D-4323-8E22-1267AA06615E>