Re: Inability to build FreeBSD-current amd64

From: Thomas Mueller <mueller6722_at_twc.com>
Date: Sat, 18 May 2019 07:17:05 +0000
from Niclas Zeising:


So now I wonder why I failed four times straight building current.  One definition of insanity is doing the same thing repeatedly and expecting a different result.

Maybe the build host, 11.1-STABLE from July 30, 2017, was too old?  I wouldn't have thought it was too old.

I could also try an old current host from August 2, 2017, or try to build 12-STABLE from my 11.1-STABLE host.  Would I do better to build amd64 or i386 from amd64 host?  I presently have no FreeBSD i386 installation, only amd64.

I can't quote anything from your message because of problems with mutt on xterm; this is NetBSD 8.99.39 amd64 with icewm.

But here is the relevant error message, I believe:

===> usr.bin/clang/llvm-mca (all)
Warning: Object directory not changed from original /usr/src/usr.bin/clang/llvm-mca
c++  -target x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin  -O2 -pipe -I/usr/src/contrib/llvm/tools/llvm-mca -I/usr/obj/usr/src/amd64.amd64/lib/clang/libllvm -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd13.0\" -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd13.0\" -DDEFAULT_SYSROOT=\"\" -DLLVM_TARGET_ENABLE_AARCH64 -DLLVM_TARGET_ENABLE_ARM -DLLVM_TARGET_ENABLE_MIPS -DLLVM_TARGET_ENABLE_POWERPC -DLLVM_TARGET_ENABLE_SPARC -DLLVM_TARGET_ENABLE_X86 -DLLVM_NATIVE_ASMPARSER=LLVMInitializeX86AsmParser -DLLVM_NATIVE_ASMPRINTER=LLVMInitializeX86AsmPrinter -DLLVM_NATIVE_DISASSEMBLER=LLVMInitializeX86Disassembler -DLLVM_NATIVE_TARGET=LLVMInitializeX86Target -DLLVM_NATIVE_TARGETINFO=LLVMInitializeX86TargetInfo -DLLVM_NATIVE_TARGETMC=LLVMInitializeX86TargetMC -ffunction-sections -fdata-sections -g
 line-tables-only -MD -MF.depend.Views_DispatchStatistics.o -MTViews/DispatchStatistics.o -fstack-protector-strong -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments  -fno-exceptions -fno-rtti -std=c++11 -stdlib=libc++ -Wno-c++11-extensions  -c /usr/src/contrib/llvm/tools/llvm-mca/Views/DispatchStatistics.cpp -o Views/DispatchStatistics.o
error: unable to open output file 'Views/DispatchStatistics.o': 'No such file or directory'
1 error generated.
*** Error code 1

I switched to the other computer with an installation of FreeBSD-current from August 2, 2017, and managed to succeed.

I had the same mergemaster problem cited in another thread, copied etc/master.passwd and etc/group from the 12-STABLE src tree.

That enabled me to successfully get through the update, but the result was a strong negative selling point for FreeBSD: no internet access.

Ethernet (re) would not connect, Hiro H50191 USB wi-fi adapter gave "Device not configured" as rsu0, and Edimax USB wi-fi adapter dropped the connection as I was trying the dhclient or ifconfig step.  Only other thing I could try is urndis with my mobile phone as access point.  I really ought to try that on FreeBSD and/or NetBSD.

I thought maybe the lack of etc/master.passwd and etc/group in src tree was a fault of subversion on NetBSD from pkgsrc as opposed to subversion on FreeBSD from ports, but browsing svnweb.freebsd.org/base/head revealed that master.passwd and group had indeed been moved, and mergemaster had not been appropriately updated.

Tom
Received on Sat May 18 2019 - 05:16:20 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:20 UTC