All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 30] Compilation error while disabling crypto device library
Date: Wed, 02 May 2018 07:28:45 +0000	[thread overview]
Message-ID: <bug-30-3@http.dpdk.org/tracker/> (raw)

https://dpdk.org/tracker/show_bug.cgi?id=30

            Bug ID: 30
           Summary: Compilation error while disabling crypto device
                    library
           Product: DPDK
           Version: 18.02
          Hardware: x86
                OS: All
            Status: CONFIRMED
          Severity: minor
          Priority: Normal
         Component: cryptodev
          Assignee: dev@dpdk.org
          Reporter: wisamm@mellanox.com
  Target Milestone: ---

How to reproduce:

Just set crypto lib to be no instead of yes:
"""
CONFIG_RTE_LIBRTE_CRYPTODEV=n
"""

Then compile.
The compilation error log:
"""
/download/dpdk/lib/librte_security/rte_security.h:57:24: fatal error:
rte_crypto.h: No such file or directory
compilation terminated.
/download/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target
'rte_security.o' failed
make[5]: *** [rte_security.o] Error 1
make[5]: *** Waiting for unfinished jobs....
  CC rte_distributor_match_sse.o
  CC rte_pdump.o
  CC rte_kni.o
  CC gso_tunnel_tcp4.o
  CC rte_distributor.o
/download/dpdk/mk/rte.subdir.mk:35: recipe for target 'librte_security' failed
make[4]: *** [librte_security] Error 2
make[4]: *** Waiting for unfinished jobs....
  SYMLINK-FILE include/rte_gso.h
  CC gso_common.o
  CC rte_gso.o
  CC gso_tcp4.o
  SYMLINK-FILE include/rte_ip_frag.h
  CC rte_ipv6_fragmentation.o
  CC rte_ipv4_reassembly.o
  CC rte_ipv4_fragmentation.o
  CC rte_ipv6_reassembly.o
  CC ip_frag_internal.o
  CC rte_ip_frag_common.o
/download/dpdk/lib/librte_vhost/vhost_crypto.c:8:27: fatal error:
rte_cryptodev.h: No such file or directory
compilation terminated.
/download/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target
'vhost_crypto.o' failed
make[5]: *** [vhost_crypto.o] Error 1
make[5]: *** Waiting for unfinished jobs....
  AR librte_bitratestats.a
  INSTALL-LIB librte_bitratestats.a
  AR librte_latencystats.a
  INSTALL-LIB librte_latencystats.a
  AR librte_gro.a
  INSTALL-LIB librte_gro.a
  AR librte_eventdev.a
  INSTALL-LIB librte_eventdev.a
  AR librte_ip_frag.a
  INSTALL-LIB librte_ip_frag.a
  AR librte_rawdev.a
  INSTALL-LIB librte_rawdev.a
  AR librte_gso.a
  INSTALL-LIB librte_gso.a
  AR librte_kni.a
  INSTALL-LIB librte_kni.a
  AR librte_pdump.a
  INSTALL-LIB librte_pdump.a
  AR librte_distributor.a
  INSTALL-LIB librte_distributor.a
/download/dpdk/mk/rte.subdir.mk:35: recipe for target 'librte_vhost' failed
make[4]: *** [librte_vhost] Error 2
/download/dpdk/mk/rte.sdkbuild.mk:49: recipe for target 'lib' failed
make[3]: *** [lib] Error 2
/download/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
make[2]: *** [all] Error 2
/download/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
make[1]: *** [pre_install] Error 2
/download/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
make: *** [install] Error 2
"""

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-05-02  7:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-30-3@http.dpdk.org/tracker/ \
    --to=bugzilla@dpdk.org \
    --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.