Date: Fri, 05 Feb 2021 08:53:08 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 251570] Release script passes CPUTYPE variable to both host and target build from MAKE_CONF file Message-ID: <bug-251570-227-nXVcY5MIqx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251570-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251570 --- Comment #6 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #5) By the way, for self hosted (not cross builds) I use the likes of: # Use of the .clang 's here avoids # interfering with other C<?>FLAGS # usage, such as ?= usage. CFLAGS.clang+= -mcpu=cortex-a72 CXXFLAGS.clang+= -mcpu=cortex-a72 CPPFLAGS.clang+= -mcpu=cortex-a72 ACFLAGS.arm64cpuid.S+= -mcpu=cortex-a72+crypto ACFLAGS.aesv8-armx.S+= -mcpu=cortex-a72+crypto ACFLAGS.ghashv8-armx.S+= -mcpu=cortex-a72+crypto This requires that the the implicit -march= value to be compatible with the host. (I've never faced a context with strongly related -march values, such as a -march=armv8-a host trying to compile to target -march=armv8.2-a instruction set extensions that an armv8-a would reject. TARGET and TARGET_ARCH are not that detailed but determine what is considered a cross-build in the build system.) -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251570-227-nXVcY5MIqx>