From: "Stanisław Kardach" <kda@semihalf.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
David Marchand <david.marchand@redhat.com>, dev <dev@dpdk.org>,
upstream@semihalf.com, Aaron Conole <aconole@redhat.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [PATCH 0/3] Fix xmm_t to rte_xmm_t scalar conversion
Date: Tue, 21 Jun 2022 14:37:51 +0200 [thread overview]
Message-ID: <CALVGJWJJzpLa4L3aH_V+m7BAK8_-uxJXMfBwg8Bco647J=Mo+w@mail.gmail.com> (raw)
In-Reply-To: <3457544.ZfL8zNpBrT@thomas>
On Tue, Jun 21, 2022 at 1:53 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> <snip>
> If it is made intentionally hard, it is just a wrong design.
> A toolchain prefix is just a name.
> We can have 2 toolchains compiled with the same name and different behaviours.
> And we can have 2 similar toolchains with a different name.
I don't think meson will allow it anytime soon (see [1]). The
reasoning being that it's easy to screw up the environment and not
notice it where as files are persistent.
>
> > So should the direction be environment or rather separating
> > cross-files into arch-part and toolchain-parts and letting user create
> > his own toolchain part while maintaining a matrix of supported
> > combinations for CI? I'm not advocating either, just want to wrap my
> > head around it.
>
> We should be able to use a toolchain compiled anywhere
> without modifying the cross files, just because a "-gnu-" is missing
> or any other irrelevant detail.
I've checked that if I remove the binaries from a cross-file, then
specifying CC/CXX/AR/STRIP environment variables is picked up by
meson:
AR=riscv64-unknown-linux-gnu-ar \
STRIP=riscv64-unknown-linux-gnu-strip \
CC=riscv64-unknown-linux-gnu-gcc \
CXX=riscv64-unknown-linux-gnu-g++ \
meson build-rv-test --cross-file=config/riscv/riscv64_linux_gcc
But then there are no default values.
A suggested frankenstein-like solution in [1] is to use a script that
generates a cross-file with [constants] section and launches meson
with it.
[1] https://github.com/mesonbuild/meson/issues/9#issuecomment-381410972
next prev parent reply other threads:[~2022-06-21 12:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 12:16 Stanislaw Kardach
2022-06-09 12:16 ` [PATCH 1/3] eal/riscv: fix xmm_t casting for C++ Stanislaw Kardach
2022-06-13 9:29 ` David Marchand
2022-06-09 12:17 ` [PATCH 2/3] lpm: fix xmm_t casting for C++ in scalar version Stanislaw Kardach
2022-06-13 9:29 ` David Marchand
2022-06-09 12:17 ` [PATCH 3/3] ci: use crossbuild-essential-riscv64 for compiling Stanislaw Kardach
2022-06-13 9:29 ` David Marchand
2022-06-14 12:31 ` Aaron Conole
2022-06-15 7:25 ` [PATCH 0/3] Fix xmm_t to rte_xmm_t scalar conversion David Marchand
2022-06-20 22:54 ` David Christensen
2022-06-21 9:30 ` Stanisław Kardach
2022-06-21 9:38 ` Bruce Richardson
2022-06-21 9:42 ` Stanisław Kardach
2022-06-21 9:49 ` Bruce Richardson
2022-06-21 10:22 ` Thomas Monjalon
2022-06-21 11:05 ` Stanisław Kardach
2022-06-21 11:53 ` Thomas Monjalon
2022-06-21 12:37 ` Stanisław Kardach [this message]
2022-06-21 14:20 ` Bruce Richardson
2022-06-21 19:48 ` Tyler Retzlaff
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='CALVGJWJJzpLa4L3aH_V+m7BAK8_-uxJXMfBwg8Bco647J=Mo+w@mail.gmail.com' \
--to=kda@semihalf.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=upstream@semihalf.com \
/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;
as well as URLs for NNTP newsgroup(s).