All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Adrian Schollmeyer <a.schollmeyer@syseleven.de>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: [PATCH v2] build: fix cross compilation to x86_64
Date: Tue, 13 Oct 2026 09:49:32 +0200	[thread overview]
Message-ID: <gO2lw07QSVubxmsBdHTdeg@monjalon.net> (raw)
In-Reply-To: <20261007092637.916513-1-a.schollmeyer@syseleven.de>

07/10/2026 11:26, Adrian Schollmeyer:
> 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>
> ---
> 
> v2 changes:
> 
>  * more explicit comment about GCC/Clang requiring x86-64
>  * switch to x86-64-v2 feature level
> 
>  config/meson.build | 6 ++++++
>  1 file changed, 6 insertions(+)

Can this change be in config/x86/meson.build ?




  parent reply	other threads:[~2026-10-13  7:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 12:59 [PATCH] build: fix cross compilation to x86_64 Adrian Schollmeyer
2026-10-05 13:14 ` 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
2026-10-13  7:49   ` Thomas Monjalon [this message]
2026-10-13  8:27     ` Adrian Schollmeyer

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=gO2lw07QSVubxmsBdHTdeg@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.