Date: Wed, 11 Jul 2018 09:03:02 -0700 From: Mark Millard <marklmi@yahoo.com> To: tech-lists <tech-lists@zyxst.net> Cc: Brian Scott <bscott@bunyatech.com.au>, freebsd-arm@freebsd.org Subject: Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3 Message-ID: <E6FA4DA3-9F9B-4B7D-B508-A736EF7EC004@yahoo.com> In-Reply-To: <7f412994-c0c5-6e91-264d-02bc5557b6bb@zyxst.net> References: <a68f6312-c9a3-2e5e-2216-bfa3b1df9a70@zyxst.net> <65245a1f-1457-6c2e-699e-132af53adf0e@bunyatech.com.au> <7f412994-c0c5-6e91-264d-02bc5557b6bb@zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-Jul-11, at 7:10 AM, tech-lists <tech-lists at zyxst.net> wrote: > On 11/07/2018 13:10, Brian Scott wrote: >> Same happened to me on 336007 last week. I put armv8crypto into >> WITHOUT_MODULES in make.conf because I needed the build for other = reasons. >=20 > I guess it should build as rpi3+ is Cortex-A53 which is ARMv8.0-A. = I'll file a bug report Bugzilla 220125 (from over a year ago) is a non-fixed report about this = for the likes of: make kernel-toolchain buildkernel Over the time since then the workaround was to use: make buildworld buildkernel buildworld put the needed stdint.h in place, kernel-toolchain did not. If kernel-toolchain was in use, then the recent bugzilla 229702 and this exchange is a duplicate. If buildworld was in use then 229702 and this exchange is new. =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?E6FA4DA3-9F9B-4B7D-B508-A736EF7EC004>