From owner-freebsd-arm@freebsd.org Fri Feb 16 19:18:08 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 87AF8F0A247 for ; Fri, 16 Feb 2018 19:18:08 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic316-8.consmr.mail.gq1.yahoo.com (sonic316-8.consmr.mail.gq1.yahoo.com [98.137.69.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EBDD86D5E8 for ; Fri, 16 Feb 2018 19:18:07 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: vOOC9ngVM1nOoIHndIbyXQzsY9GJ265A6wUHZ9HK3Jk1IQoo4enn6C35eeRFN7N bZ3o6kSFRJloQIaLuOVvbenP6MrW3TiHywjy8L3A9FxjMECQ0ipdv90kk1A7vrkXP4mak_30NR4Q hNKYkVmY0heBee_tYK6uCC_BbN146_QNBgyg1ix1P3Xxbo_unGkc2FZ7bjTGoQiJOpI2u5hIlXfQ Xh7sBbAVce9MGW2dCeOS5Eaq1ff3TPq2xBCxWbfMQ4jVdBDzoY4oEcsh4FI3GakcyFP.cWxUh432 xRIw7e2WYf9N93hSiqkZSYrNUFM8WkfBDypxl3SJuvfnHIQA9dn3xAiVIaUd0Sn1J7OvNwleJbAA o6HYFMr798gJfpvW7eYqkevjx2RHtZ1fcP8B_bPxj8z7k.pjtJ3PsN8hwbJf7OlulpvxUij.Odzq nMOeCdtpSgLA4CCCv7lQsGCxVoWNq4qbUN8Yg7xFdkZl.WlcfhNA24RGhNQWjPuxnxpPOghc4BQ2 2LXaUWypwNvTknKlfVw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Fri, 16 Feb 2018 19:18:00 +0000 Received: from smtp107.rhel.mail.gq1.yahoo.com (EHLO [192.168.1.25]) ([10.211.35.149]) by smtp413.mail.gq1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 90efe63cffcfa20e7f042288e9ec1f03; Fri, 16 Feb 2018 18:57:41 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: RPI3 can't build kernel-toolchain From: Mark Millard In-Reply-To: <20180216170927.GA88394@www.zefox.net> Date: Fri, 16 Feb 2018 10:57:40 -0800 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3F0B778A-E33E-474B-B4AF-73A167F27E36@yahoo.com> References: <20180212183256.GA75467@www.zefox.net> <20180216060337.GA88230@www.zefox.net> <11F7E450-097C-41B3-B494-73106C710AE7@yahoo.com> <20180216170927.GA88394@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3445.5.20) 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 19:18:08 -0000 On 2018-Feb-16, at 9:09 AM, bob prohaska 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 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 >>> ^~~~~~~~~~ >>> 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 = >>=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)