Date: Fri, 16 Feb 2018 09:09:27 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi26-fbsd@yahoo.com> Cc: freebsd-arm@freebsd.org, bob prohaska <fbsd@www.zefox.net> Subject: Re: RPI3 can't build kernel-toolchain Message-ID: <20180216170927.GA88394@www.zefox.net> In-Reply-To: <11F7E450-097C-41B3-B494-73106C710AE7@yahoo.com> References: <20180212183256.GA75467@www.zefox.net> <20180216060337.GA88230@www.zefox.net> <11F7E450-097C-41B3-B494-73106C710AE7@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 16, 2018 at 06:19:15AM -0800, Mark Millard wrote: > > On 2018-Feb-15, at 10:03 PM, bob prohaska <fbsd@www.zefox.net> wrote: > > > On Mon, Feb 12, 2018 at 10:32:56AM -0800, bob prohaska wrote: > > > > Updating sources eventually allowed make kernel-toolchain to build without > > errors. However, make buildkernel still stops, reporting > > > > In file included from /usr/src/sys/crypto/armv8/armv8_crypto_wrap.c:46: > > /usr/obj/usr/src/arm64.aarch64/tmp/usr/lib/clang/6.0.0/include/arm_neon.h:31:10: fatal error: 'stdint.h' file not found > > #include <stdint.h> > > ^~~~~~~~~~ > > 1 error generated. > > *** [armv8_crypto_wrap.o] Error code 1 > > > > See FreeBSD bugzilla 220125: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125>; > > You can hand patch the tree (similar to comment 3 but for > the clang version in use). Later comments have notes about > various places the file might go. > Running cp ./contrib/llvm/tools/clang/lib/Headers/stdint.h /usr/lib/clang/6.0.0/include didn't solve the problem. Using cp /usr/lib/include/stdint.h /usr/obj/usr/src/arm64.aarch64/tmp/usr/include/ does seem to be working. Since this is a self-hosted compile there's hope the resulting kernel will be more stable than r328935. Am I correct in thinking that arm does not correctly recognize when it's self-hosting? Doubtless I'm being naive, but shouldn't that be a fairly straightforward determination? Armv7 gave hints of the same problem, asking that TARGET_ARCH be set in a self-hosting buildworld. That's seemingly fixed, now. Thanks very much! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180216170927.GA88394>