Lev Serebryakov <l...@freebsd.org> writes: > Hello Freebsd-ports, > > I'm confused, should I use "arm64" or "aarch64" and how to spell > mips(el?)(64?32?) properly.
${ARCH} ~ ${MACHINE_ARCH} (uname -p). As the ports framework doesn't
expose ${MACHINE} (uname -m) you're stuck listing every supported
arm/mips flavor unless you override e.g.,
ONLY_FOR_ARCHS= aarch64 amd64 arm armeb armv6 armv6hf i386 \
mips mips64 mips64el mipsel mipsn32 powerpc \
powerpc64 sparc64
vs.
ARCH= ${MACHINE}
ONLY_FOR_ARCHS= amd64 arm arm64 i386 mips pc98 powerpc sparc64
# Translates to MACHINE/MACHINE_ARCH during runtime
$ make targets -C /usr/src
Supported TARGET/TARGET_ARCH pairs for world and kernel targets
amd64/amd64
arm/arm
arm/armeb
arm/armv6
arm/armv6hf
arm64/aarch64
i386/i386
mips/mipsel
mips/mips
mips/mips64el
mips/mips64
mips/mipsn32
pc98/i386
powerpc/powerpc
powerpc/powerpc64
sparc64/sparc64
--
MACHINE and MACHINE_ARCH are defined by make(1) itself but not
documented in the man page.
signature.asc
Description: PGP signature
