DPDK usage discussions
 help / color / mirror / Atom feed
From: gary <apriloffice@163.com>
To: users <users@dpdk.org>
Subject: Re: [dpdk-users] Using intel-ipsec-mb to compile dpdk
Date: Mon, 27 Sep 2021 14:31:17 +0800	[thread overview]
Message-ID: <202109271431053914734@163.com> (raw)
In-Reply-To: <2021092711170335101722@163.com>

sorry  ,  I had make it work




Hi,
 
I  try to run l2fwd-crypto with use SNOW3G poll mode driver , I am using DPDK 19.11 ,which can be patched to use intel-ipsec-mb. and  the version is intel-ipsec-mb-1.0, but when i trying out dpdk ,there is an error hit as below:

  == Build drivers/crypto/octeontx2
  CC otx2_cryptodev.o
  PMDINFO otx2_cryptodev.o.pmd.c
  CC otx2_cryptodev.o.pmd.o
  LD otx2_cryptodev.o
  CC otx2_cryptodev_capabilities.o
  CC otx2_cryptodev_hw_access.o
  CC otx2_cryptodev_mbox.o
  CC otx2_cryptodev_ops.o
  AR librte_pmd_octeontx2_crypto.a
  INSTALL-LIB librte_pmd_octeontx2_crypto.a
== Build drivers/crypto/scheduler
  SYMLINK-FILE include/rte_cryptodev_scheduler_operations.h
  SYMLINK-FILE include/rte_cryptodev_scheduler.h
  CC scheduler_pmd.o
  CC scheduler_pmd_ops.o
  CC rte_cryptodev_scheduler.o
  CC scheduler_roundrobin.o
  CC scheduler_pkt_size_distr.o
  CC scheduler_failover.o
  CC scheduler_multicore.o
  AR librte_pmd_crypto_scheduler.a
  INSTALL-LIB librte_pmd_crypto_scheduler.a
== Build drivers/crypto/snow3g
/home/gary/test/0903-t/components/3rdparty/openfastpath-2.0/archive/fastpath/dpdk/drivers/crypto/snow3g/Makefile:36: *** "IPSec_MB version >= 0.53 is required".  Stop.
make[3]: *** [snow3g] Error 2
make[2]: *** [crypto] Error 2
make[1]: *** [drivers] Error 2
make: *** [all] Error 2


      please suggest how I can do to solve this err 
      ths

      Regards,
      gary



      reply	other threads:[~2021-09-27  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27  3:17 apriloffice
2021-09-27  6:31 ` gary [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=202109271431053914734@163.com \
    --to=apriloffice@163.com \
    --cc=users@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;
as well as URLs for NNTP newsgroup(s).