From: Gabor LENCSE <lencse@hit.bme.hu>
To: users@dpdk.org
Subject: [dpdk-users] How can I update the compilation of my 16.11.11-1+deb9u2 version DPDK project to 18.11.11-1~deb10u1
Date: Mon, 5 Jul 2021 16:14:42 +0200 [thread overview]
Message-ID: <390f368b-bfc2-e725-31e2-7cab1ac13f01@hit.bme.hu> (raw)
Dear DPDK Users,
I hope that I am writing to the right place, I have just signed to this
mailing list.
I have written siitperf, a DPDK-based, RFC 8219 compliant SIIT tester:
https://github.com/lencsegabor/siitperf/
Currently, I can compile it under Debian 9 (DPDK version is:
16.11.11-1+deb9u2) using the following Makefile, which I wrote on the
basis of an example:
https://github.com/lencsegabor/siitperf/blob/master/Makefile-tp
It needs the environment variables set by the
/usr/share/dpdk/dpdk-sdk-env.sh, which is a part of the version
16.11.11-1+deb9u2 "dpdk-dev" Debian package.
However, I need to use Debian 10 instead of Debian 9, for hardware
support issues.
Unfortunately, I have experienced, that the dpdk-sdk-env.sh file is
missing from DPDK 18.11.11.
( I have also read that dpdk-sdk-env.sh is no longer included:
https://linux.debian.bugs.dist.narkive.com/gOb82oOD/bug-921043-dpdk-dev-dpdk-sdk-env-sh-no-longer-included-in-dpdk-dev
.)
Of course, I could set the environment variables manually as follows:
export RTE_TARGET="x86_64-default-linuxapp-gcc"
export RTE_SDK="/usr/share/dpdk/"
export RTE_INCLUDE="/usr/include/dpdk"
However it does not help:
root@tester:~/siitperf# make
Makefile:54: /usr/share/dpdk//mk/rte.extapp.mk: No such file or directory
make: *** No rule to make target '/usr/share/dpdk//mk/rte.extapp.mk'. Stop.
root@tester:~/siitperf# find / -name rte.extapp.mk
root@tester:~/siitperf#
As you can see, "rte.extapp.mk" does not exist any more.
Could anyone help me, how to compile my project under DPDK 18.11.11?
Thank you very much for your help in advance!
Best regards,
Gábor Lencse
reply other threads:[~2021-07-05 14:14 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=390f368b-bfc2-e725-31e2-7cab1ac13f01@hit.bme.hu \
--to=lencse@hit.bme.hu \
--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).