From owner-freebsd-arm@freebsd.org Fri Feb 16 17:09:24 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28BDEF00A37 for ; Fri, 16 Feb 2018 17:09:24 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 97290864A2 for ; Fri, 16 Feb 2018 17:09:23 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w1GH9RbX090277 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 16 Feb 2018 09:09:29 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w1GH9RPQ090276; Fri, 16 Feb 2018 09:09:27 -0800 (PST) (envelope-from fbsd) Date: Fri, 16 Feb 2018 09:09:27 -0800 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3 can't build kernel-toolchain Message-ID: <20180216170927.GA88394@www.zefox.net> References: <20180212183256.GA75467@www.zefox.net> <20180216060337.GA88230@www.zefox.net> <11F7E450-097C-41B3-B494-73106C710AE7@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11F7E450-097C-41B3-B494-73106C710AE7@yahoo.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 17:09:24 -0000 On Fri, Feb 16, 2018 at 06:19:15AM -0800, Mark Millard wrote: > > On 2018-Feb-15, at 10:03 PM, bob prohaska 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 > > ^~~~~~~~~~ > > 1 error generated. > > *** [armv8_crypto_wrap.o] Error code 1 > > > > See FreeBSD bugzilla 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