Date: Sun, 02 Apr 2023 23:58:01 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 258358] Fails to build on riscv: arm_bf16.h: sh: clang-tblgen: Exec format error Message-ID: <bug-258358-29464-wqDdGZ1UYq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258358-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-258358-29464@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=3D258358 --- Comment #18 from Robert Clausecker <fuz@FreeBSD.org> --- (In reply to Mark Millard from comment #17) Such a procedure requires disassembling the machine to access the storage f= rom another device and is thus fairly cumbersome. Last time I checked, upgradi= ng does not really work with this mechanism either as upgrading involves runni= ng some binaries to merge configuration and such, which doesn't work when cross-building. It is additionally not documented anywhere. Is this really how we want things to be? It is a reasonable expectation that any FreeBSD system should be able to upgrade itself following procedures given in the handbook with no external computer needed. Yes, upgrading is important to me. I absolutely do not w= ant to set up the system anew every time a new release comes out. This is repulsive and a huge waste of time. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258358-29464-wqDdGZ1UYq>