From owner-freebsd-bugs@freebsd.org Tue Oct 10 09:41:47 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 929DEE2AC17 for ; Tue, 10 Oct 2017 09:41:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F719748E7 for ; Tue, 10 Oct 2017 09:41:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9A9flUj052470 for ; Tue, 10 Oct 2017 09:41:47 GMT (envelope-from bugzilla-noreply@freebsd.org) 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 Date: Tue, 10 Oct 2017 09:41:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2017 09:41:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220125 --- Comment #4 from Mark Millard --- (In reply to Heinz N. Gies from comment #3) I do not expect that the working "buildworld" puts a stdint.h in /usr/lib/clang/5.0.0/include/ so I do not expect that that is the right place. I do expect that kernel-toolchain should put one of more stdint.h files in place(s) that buildworld does put such. Note: It looks like my description's # ls -dlT . . ./arm64.aarch64/usr/src/include/* was incoherent. It should have exposed the areas that were found to have stdint.h in the buildworld example: . . ./arm64.aarch64/usr/src/tmp/usr/include/sys/stdint.h . . ./arm64.aarch64/usr/src/tmp/usr/include/c++/v1/stdint.h . . ./arm64.aarch64/usr/src/tmp/usr/include/c++/v1/tr1/stdint.h . . ./arm64.aarch64/usr/src/tmp/usr/include/stdint.h In general buildworld and the like should not be using the live systems copies of files directly: they might have been updated for the new version being built. So normally they would be found under arm.aarch64/. . . someplace. Also clang/5.0.0/include/ probably does not get system specific files normally but various architectures have somewhat differing stdint.h content (such as for 32-bit vs. 64-bit). . . ./arm64.aarch64/usr/src/tmp/usr/include/stdint.h is an example of a architecture specific path for finding architecture specific content and so would seem more likely. --=20 You are receiving this mail because: You are the assignee for the bug.=