Date: Tue, 10 Oct 2017 10:13:39 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file not found Message-ID: <bug-220125-8-4wEplPFi2m@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220125-8@https.bugs.freebsd.org/bugzilla/> References: <bug-220125-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220125 --- Comment #6 from Mark Millard <markmi@dsl-only.net> --- (In reply to Heinz N. Gies from comment #5) If the build-host system type is the same as the build-target system type and stdint.h has not actually changed then /usr/lib/include/stdint.h content may well actually be correct content. But if stdint.h has changed (unlikely?) or or the build is a cross build then the /usr/lib/include/stdint.h content would more likely be wrong in some way. But that way need not make the build abort: it may just build something that is wrong in some way. In my examples such as: . . ./arm64.aarch64/usr/src/tmp/usr/include/stdint.h the arm64.aarch64 is the build-target type. (FreeBSD normally only produces such x.y naming in the paths for cross builds.) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220125-8-4wEplPFi2m>