Date: Mon, 4 Dec 2023 07:10:27 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: aarch64: sysutils/cpu-x@ncurses got SIGSEGV during its initial print_activecore Message-ID: <ZW17Y-1qBe3nYZd7@FreeBSD.org> In-Reply-To: <5D09C706-6A51-472A-A35C-E50007AA2F53@yahoo.com> References: <2A081516-C014-48B4-968B-84C198B7D2B2@yahoo.com> <5D09C706-6A51-472A-A35C-E50007AA2F53@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 02, 2023 at 11:26:04PM -0800, Mark Millard wrote: > Hmm. On thinking about it, the output: > > # cpu-x > CPU-X:core.c:301: failed to call libcpuid (CPUID instruction is not supported) > CPU-X:core.c:1478: failed to find chipset vendor and model > CPU-X:core.c:1480: failed to find graphic card vendor and model > CPU-X:core.c:2260: failed to retrieve CPU temperature (fallback mode) > > that also occured may be more of an indication that aarch64 is not > actually supported by the infrastructure used. Indeed it is not. Perhaps it's time to teach libcpuid about aarch64? :) > The Makefile should possibly block doing aarch64 builds that will > not work. Likely more than aarch64 would have that status. Previously libcpuid was arch-restricted but I've lifted it a year ago (see commit ff7949343c4a). I guess I could leave it as "i386 amd64" again, but then people would come by and reapply commit 9482644374c1. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZW17Y-1qBe3nYZd7>