aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown/snippets
diff options
context:
space:
mode:
authorSimon McVittie <smcv@debian.org>2023-08-05 11:34:29 +0100
committerEli Schwartz <eschwartz93@gmail.com>2023-08-06 02:32:25 -0400
commitb95ebf80b85fc8ed3ba2cf828d7b96f95894a29b (patch)
tree33c66b5ca596c47f87965494bfd33f359f34530f /docs/markdown/snippets
parent2cf79c5062f553382b641f4ac8be897d532902aa (diff)
downloadmeson-b95ebf80b85fc8ed3ba2cf828d7b96f95894a29b.zip
meson-b95ebf80b85fc8ed3ba2cf828d7b96f95894a29b.tar.gz
meson-b95ebf80b85fc8ed3ba2cf828d7b96f95894a29b.tar.bz2
environment: Don't override mips64 to mips if no compilers are available
If we have a build- or host-architecture compiler, we can detect mips64 vs. mips by the fact that mips64 compilers define __mips64. However, machine_info_can_run() doesn't provide any compilers, because it is interested in the architecture of the underlying kernel. If we don't return mips64 when running on a mips64 kernel, machine_info_can_run() will wrongly say that we can't run mips64 binaries. If we're running a complete 32-bit mips user-space on a mips64 kernel, it's OK to return mips64 in the absence of any compilers, as a result of the previous commit "environment: Assume that mips64 can run 32-bit mips binaries". Resolves: https://github.com/mesonbuild/meson/issues/12017 Bug-Debian: https://bugs.debian.org/1041499 Fixes: 6def03c7 "detect_cpu: Fix mips32 detection on mips64" Signed-off-by: Simon McVittie <smcv@debian.org>
Diffstat (limited to 'docs/markdown/snippets')
0 files changed, 0 insertions, 0 deletions