Date: Fri, 16 Feb 2018 10:57:40 -0800 From: Mark Millard <marklmi26-fbsd@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: RPI3 can't build kernel-toolchain Message-ID: <3F0B778A-E33E-474B-B4AF-73A167F27E36@yahoo.com> In-Reply-To: <20180216170927.GA88394@www.zefox.net> References: <20180212183256.GA75467@www.zefox.net> <20180216060337.GA88230@www.zefox.net> <11F7E450-097C-41B3-B494-73106C710AE7@yahoo.com> <20180216170927.GA88394@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-Feb-16, at 9:09 AM, bob prohaska <fbsd@www.zefox.net> wrote: > On Fri, Feb 16, 2018 at 06:19:15AM -0800, Mark Millard wrote: >>=20 >> On 2018-Feb-15, at 10:03 PM, bob prohaska <fbsd@www.zefox.net> wrote: >>=20 >>> On Mon, Feb 12, 2018 at 10:32:56AM -0800, bob prohaska wrote: >>>=20 >>> Updating sources eventually allowed make kernel-toolchain to build = without >>> errors. However, make buildkernel still stops, reporting >>>=20 >>> 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 >>>=20 >>=20 >> See FreeBSD bugzilla 220125: >>=20 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220125 = <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220125>; >>=20 >> 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. >>=20 > Running > cp ./contrib/llvm/tools/clang/lib/Headers/stdint.h = /usr/lib/clang/6.0.0/include > didn't solve the problem.=20 >=20 > 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. >=20 > Am I correct in thinking that arm does not correctly recognize when = it's=20 > 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,=20 > now. amd64 -> aarch64 cross-builds using kernel-toolchain also failed the same way for buildkernel. In order to cross-build I used buildworld instead (after the build failed the other way). (My FreeBSD time is greatly limited compared to when I was doing that. So I've not synchronized in some time and do not directly know the current status. It has been even longer since I've done a self-hosted build for armv7, aarch64, powerpc, or powerpc64.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F0B778A-E33E-474B-B4AF-73A167F27E36>