From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: stable@dpdk.org, roy.fan.zhang@intel.com,
pablo.de.lara.guarch@intel.com, bruce.richardson@intel.com,
Declan Doherty <declan.doherty@intel.com>,
Luca Boccassi <bluca@debian.org>,
Akhil Goyal <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] drivers/crypto: fix build with make 4.3
Date: Thu, 12 Mar 2020 09:05:26 +0100 [thread overview]
Message-ID: <4305448.CvnuH1ECHv@xps> (raw)
In-Reply-To: <20200228132547.650594-1-thomas@monjalon.net>
28/02/2020 14:25, Thomas Monjalon:
> In the check for the version of intel-ipsec-mb library,
> there is a backslash in front of the #include.
> This backslash is for escaping the hash sign parsed as
> a number sign in make.
>
> Since make-4.3, escaping is not required for the number sign.
> As a consequence, it resolves now to '\#':
>
> syntax error near unexpected token `|'
> `grep -e "IMB_VERSION_STR" \#include <intel-ipsec-mb.h> | cut -d'"' -f2'
> syntax error near unexpected token `|'
> `grep -e "IMB_VERSION_NUM" \#include <intel-ipsec-mb.h> | cut -d' ' -f3'
>
> The makefiles are fixed by using a variable for the hash sign,
> as recommended in make-4.3 changelog:
> https://lists.gnu.org/archive/html/info-gnu/2020-01/msg00004.html
>
> Fixes: 3067c8ce77ac ("crypto/aesni_mb: fix build with custom dependency path")
> Fixes: 457b8e372975 ("crypto/aesni_gcm: check dependency version with make")
> Fixes: bf6eb2c22fd1 ("crypto/kasumi: use IPsec library")
> Fixes: 7c87e2d7b359 ("crypto/snow3g: use IPsec library")
> Fixes: 61f7c988e39e ("crypto/zuc: use IPsec library")
> Cc: stable@dpdk.org
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>
> v2:
> - found the root cause in make-4.3
> - use $H for compatibility with make < 4.3
>
> Note the list of "Fixes" references are here to help backporting,
> even if there was no bug before the recent release of make-4.3.
I was expecting some reviews and a merge in the crypto tree.
Given it is blocking me to merge any other patch,
after waiting 2 weeks,
Applied in master branch.
prev parent reply other threads:[~2020-03-12 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 22:33 [dpdk-dev] [PATCH] drivers/crypto: fix build with make Thomas Monjalon
2020-02-28 12:24 ` Akhil Goyal
2020-02-28 12:41 ` Thomas Monjalon
2020-02-28 12:56 ` Thomas Monjalon
2020-02-28 13:25 ` [dpdk-dev] [PATCH v2] drivers/crypto: fix build with make 4.3 Thomas Monjalon
2020-03-12 8:05 ` Thomas Monjalon [this message]
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=4305448.CvnuH1ECHv@xps \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=stable@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.