DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stefan Binna <stefan.binna@salzburgresearch.at>
To: dev@dpdk.org
Subject: [dpdk-dev] rte_config.h: No such file or directory in DPDK 2.1.0-rc3 and DPDK 2.0.0
Date: Wed, 5 Aug 2015 12:07:30 +0200	[thread overview]
Message-ID: <55C1E062.6010009@salzburgresearch.at> (raw)
In-Reply-To: <55C1C677.4040106@salzburgresearch.at>


Hi,

I am seeking help regarding DPDK 2.1.0 -rc3 as well as DPDK 2.0.0 on
Ubuntu 14.04 (Kernel 3.19.0-031900-generic) and
openvswitchdpdk.l.1.1.0-27.gz.

I can install both DPDK-versions without errors by help of following
commands:

export RTE_SDK=$(pwd)
export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
install T="$RTE_TARGET"

But when I try to compile the Open vSwitch by help of following commands:

./boot.sh
./configure RTE_SDK=$(RTE_SDK) --disable-ssl make

I always get following errors:

lib/dpdk-link.c:25:24: fatal error: rte_config.h: No such file or directory
#include <rte_config.h>

compilation terminated.
make[2]: *** [lib/dpdk-link.o] Error 1
make[2]: Directory »/root/ovs_dpdk/openvswitch« is left
make[1]: *** [all-recursive] Error 1
make[1]: Directory »/root/ovs_dpdk/openvswitch« is left
make: *** [all] Error 2

Tried Workarounds:
Workaround 1: Tried to copy the file rte_config.h (found in
dpdk/include/) manually to openvswitch/lib
Result 1: Still couldn't make the build

Workaround 2: Setting the RTE_SDK variable to
dpdk/x86_64-ivshmem-linuxapp-gcc path instead of just to dpdk path
Result 2: Still couldn't make the build

Workaround 3: Use DPDK 1.7.1
Result 3: Can't even compile DPDK 1.7.1

Thanks!
Stefan.

       reply	other threads:[~2015-08-05 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55C1C677.4040106@salzburgresearch.at>
2015-08-05 10:07 ` Stefan Binna [this message]
2015-08-05 10:14   ` Thomas Monjalon
2015-08-05 11:22     ` Stefan Binna

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=55C1E062.6010009@salzburgresearch.at \
    --to=stefan.binna@salzburgresearch.at \
    --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 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).