From: Thomas Monjalon <thomas@monjalon.net>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dev@dpdk.org, Luca Boccassi <bluca@debian.org>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v4 1/2] build: avoid non supported -march on ppc (meson)
Date: Sun, 18 Nov 2018 15:24:24 +0100 [thread overview]
Message-ID: <1788865.Bn7SiURA0A@xps> (raw)
In-Reply-To: <20181114194012.18255-1-christian.ehrhardt@canonical.com>
14/11/2018 20:40, Christian Ehrhardt:
> So far only if machine was "native" it did use the re-direction to
> not set -march on ppc64 (where -march is not supported).
> We have to use mcpu/mtune in any case on ppc for whatever someone using
> the build system defines as machine.
>
> Fixes: 54d609a13876 ("build: add ppc64 meson build")
>
> Acked-by: Luca Boccassi <bluca@debian.org>
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Series applied, thanks
next prev parent reply other threads:[~2018-11-18 14:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 11:34 [PATCH 1/2] build: avoid non supported -march on ppc (meson) Christian Ehrhardt
2018-11-14 11:34 ` [PATCH 2/2] build: establish an invariant machine type Christian Ehrhardt
2018-11-14 11:40 ` Luca Boccassi
2018-11-14 11:52 ` Bruce Richardson
2018-11-14 12:05 ` Luca Boccassi
2018-11-14 13:09 ` Christian Ehrhardt
2018-11-14 13:18 ` [PATCH] " Christian Ehrhardt
2018-11-14 13:54 ` Bruce Richardson
2018-11-14 14:33 ` [PATCH v3] " Christian Ehrhardt
2018-11-14 19:39 ` Christian Ehrhardt
2018-11-18 13:24 ` Thomas Monjalon
2018-11-14 19:40 ` [PATCH v4 1/2] build: avoid non supported -march on ppc (meson) Christian Ehrhardt
2018-11-14 19:40 ` [PATCH v4 2/2] build: establish an invariant machine type Christian Ehrhardt
2018-11-18 14:24 ` Thomas Monjalon [this message]
2018-11-14 13:06 ` [PATCH " Luca Boccassi
2018-11-14 13:08 ` Christian Ehrhardt
2018-11-14 11:39 ` [PATCH 1/2] build: avoid non supported -march on ppc (meson) Luca Boccassi
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=1788865.Bn7SiURA0A@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=christian.ehrhardt@canonical.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.