From: Adrian Schollmeyer <a.schollmeyer@syseleven.de>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Adrian Schollmeyer <a.schollmeyer@syseleven.de>
Subject: [PATCH] build: fix cross compilation to x86_64
Date: Mon, 5 Oct 2026 14:59:10 +0200 [thread overview]
Message-ID: <20261005125943.678879-1-a.schollmeyer@syseleven.de> (raw)
If x86_64 is specified as target CPU instruction set (e.g. when
cross-compiling *to* x86_64), the cpu_instruction_set may be set to
x86_64, e.g. if it is derived from a Meson crossfile. However, while
Meson uses "x86_64" as name for the x86_64 architecture, compiler
options accept only "x86-64".
Introduce a conditional for handling this special case by changing
cpu_instruction_set to the march-compatible value.
Signed-off-by: Adrian Schollmeyer <a.schollmeyer@syseleven.de>
---
config/meson.build | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/config/meson.build b/config/meson.build
index dcb84ebd13..238d6cae0c 100644
--- a/config/meson.build
+++ b/config/meson.build
@@ -177,6 +177,11 @@ if not is_ms_compiler
machine_args += '-mtune=' + cpu_instruction_set
compiler_arch_support = cc.has_argument('-mcpu=' + cpu_instruction_set)
else
+ # Meson uses x86_64, but compilers expect x86-64.
+ # See https://mesonbuild.com/Reference-tables.html#cpu-families
+ if cpu_instruction_set == 'x86_64'
+ cpu_instruction_set = 'x86-64'
+ endif
machine_args += '-march=' + cpu_instruction_set
# arm manages generic/auto config in config/arm/meson.build
if cpu_instruction_set != 'generic' and cpu_instruction_set != 'auto'
--
2.43.0
next reply other threads:[~2026-10-05 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 12:59 Adrian Schollmeyer [this message]
2026-10-05 13:14 ` [PATCH] build: fix cross compilation to x86_64 Morten Brørup
2026-10-05 14:30 ` Bruce Richardson
2026-10-07 9:26 ` [PATCH v2] " Adrian Schollmeyer
2026-10-07 10:39 ` Bruce Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261005125943.678879-1-a.schollmeyer@syseleven.de \
--to=a.schollmeyer@syseleven.de \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox