Date: Thu, 12 Jul 2018 10:44:00 +0100 From: tech-lists <tech-lists@zyxst.net> To: Mark Millard <marklmi@yahoo.com>, FreeBSD Current <freebsd-current@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org> Subject: Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3 Message-ID: <a8cc68ec-e87d-9133-7ad9-59c5b42ed749@zyxst.net> In-Reply-To: <A7BBACBB-44A1-4F95-B4F6-498B72238FC5@yahoo.com> References: <A7BBACBB-44A1-4F95-B4F6-498B72238FC5@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a8cc68ec-e87d-9133-7ad9-59c5b42ed749>