From owner-freebsd-arm@freebsd.org Fri Feb 16 14:19:28 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 E51C3F17C33 for ; Fri, 16 Feb 2018 14:19:27 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic311-21.consmr.mail.gq1.yahoo.com (sonic311-21.consmr.mail.gq1.yahoo.com [98.137.65.202]) (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 67AD07BE26 for ; Fri, 16 Feb 2018 14:19:27 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: KmOBGZoVM1l3yRdMRhMxjiErvIdyW2GgibFvSUH07nNapT7bp2B4gRJAi7llFo6 X5.NJJW8N8hdxqwqXYtWLkslNFEbF4vNlzLo5vvoGes2uJkdH_sG4RHCSTDfUQ31RMosS5mrQDQ1 9C2eNB_Fm5u4Gyqlk.V9Bqsj29IA9n1CIXr4nK4LAR2xdLaJH8mn06Bw9t9zKNYNQ2043C1sOV92 5woappJ_BsenInNk2mj041Fg8xiP_pY6P6MYY2HWy_YDv7c76QhiRs4eOK9SbTXzTPwph7a9FJmh HzIZllW1gutCMR5N9Q0efDk7IY9022jfNf2DiK3Sd6NmYwFkFel8rv2Kt36QzvMLjD37lofKY0.1 KjYijnSrqZWCgKLb5_fcECC_d9S4iqNHAQeHzuaf3ONU7GwiNl8Y07ScjXlakwWTxLnf6rnOt8MD _fZunQpmBXMn5SKCs2MQ4AkhEN1fdW6LoSO7euc0qodKNWwwIsbSqfSqgQgPP66_bWGq.E8ytg5s QNuJ0PxjJl3IBwKx09g-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Fri, 16 Feb 2018 14:19:20 +0000 Received: from smtp102.rhel.mail.gq1.yahoo.com (EHLO [192.168.1.25]) ([216.39.57.211]) by smtp404.mail.gq1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 9889ff7fc9afd1646b3d4cfd9e387434; Fri, 16 Feb 2018 14:19:16 +0000 (UTC) From: Mark Millard Message-Id: <11F7E450-097C-41B3-B494-73106C710AE7@yahoo.com> Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: RPI3 can't build kernel-toolchain Date: Fri, 16 Feb 2018 06:19:15 -0800 In-Reply-To: <20180216060337.GA88230@www.zefox.net> Cc: freebsd-arm@freebsd.org To: bob prohaska References: <20180212183256.GA75467@www.zefox.net> <20180216060337.GA88230@www.zefox.net> X-Mailer: Apple Mail (2.3445.5.20) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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 14:19:28 -0000 On 2018-Feb-15, at 10:03 PM, bob prohaska wrote: > On Mon, Feb 12, 2018 at 10:32:56AM -0800, bob prohaska wrote: >> On a Pi3 running r328935 trying to build sources at 329171 a=20 >> make -j2 kernel-toolchain fails with >> /usr/bin/ld: error: duplicate symbol:=20 >>>>> defined at ASTImporter.o:() in archive = /usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libclang/libclang.a= >>=20 >=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 > This seems rather odd, since find reports files with that name in > several locations within /usr/src: >=20 > root@www:/usr/src # find . -name stdint.h -depth -print > ./sys/sys/stdint.h > ./sys/contrib/zstd/lib/freebsd/stdint.h > ./contrib/llvm/tools/clang/lib/Headers/stdint.h > ./contrib/libc++/include/stdint.h > ./contrib/libstdc++/include/tr1/stdint.h >=20 > To the best of my ability the source tree is unmolested, svnlite info = reports: > root@www:/usr/src # svnlite status . > ? buildkernel.log > ? buildscript > ? installscript > ? kernelscript > ? toolchain.log > ? toolchainscript > root@www:/usr/src #=20 >=20 > The source tree is presently at r329360. See FreeBSD bugzilla 220125: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220125 = 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. If you can get buildworld to work, it will put stdint.h in the right = place. The places that you list are not the places the compiles actively look = in. See comment 9 for the difference between buildworld and kernel-toolchain for where the file is placed. kernel-toolchain does not do the right thing for arm_neon.h to work; arm-neon.h presumes that header, which is not normally part of a FreeBSD kernel build. Your report tells me that this is currently unresolved. =3D=3D=3D Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late)