From: Jamie Fargen <jfargen@redhat.com>
To: Rami Rosen <roszenrami@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] TestPMD testing with VMX3NET Devices...
Date: Fri, 7 Sep 2018 10:38:39 -0400 [thread overview]
Message-ID: <CAB-EjEJp3a=ptT_LD8WUbnWk1nDfkT++mDiqthRP=ioB0cqR5Q@mail.gmail.com> (raw)
In-Reply-To: <CAKoUArn3j4RADz++C0p1r9LH2bcqXDuk=juvH_0F_=isO78j9Q@mail.gmail.com>
Rami-
The output show that that CONFIG_RTE_BUILD_SHARED_LIB is set to no.
# cat build/.config | grep -i shared CONFIG_RTE_BUILD_SHARED_LIB
CONFIG_RTE_BUILD_SHARED_LIB=n
I wil l change that to CONFIG_RTE_BUILD_SHARED_LIB=y and reinstall.
Regards,
-Jamie
On Fri, Sep 7, 2018 at 9:52 AM, Rami Rosen <roszenrami@gmail.com> wrote:
> Hi, Jamie,
> By default, building in DPDK (including in stable-17.11.4) is by creating
> static
> libs (*.a) and not shared libs (*so).
>
> What does cat build/.config | grep -i shared show ?
> If you have CONFIG_RTE_BUILD_SHARED_LIB=y, this means that
> you use shared libs, and in such a case, a VMXNET3 *.so should be
> generated in the build
> (librte_pmd_vmxnet3_uio.so), and if indeed the testpmd app you use was
> built in
> a tree where CONFIG_RTE_BUILD_SHARED_LIB is "y",
> then the librte_pmd_vmxnet3_uio.so should be under /usr/lib64/... folder
> so it will work.
> It seems that the best thing is to rebuild the DPKD tree (after make
> clean) and reinstall it.
>
> Regards,
> Rami Rosen
>
--
Jamie Fargen
Senior Consultant
jfargen@redhat.com
813-817-4430
next prev parent reply other threads:[~2018-09-07 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 16:39 Jamie Fargen
2018-09-07 13:08 ` Rami Rosen
2018-09-07 13:22 ` Jamie Fargen
2018-09-07 13:52 ` Rami Rosen
2018-09-07 14:38 ` Jamie Fargen [this message]
2018-09-07 15:20 ` Jamie Fargen
2018-09-07 15:44 ` Rami Rosen
2018-09-07 17:24 ` Emre Eraltan
2018-09-07 18:06 ` Jamie Fargen
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='CAB-EjEJp3a=ptT_LD8WUbnWk1nDfkT++mDiqthRP=ioB0cqR5Q@mail.gmail.com' \
--to=jfargen@redhat.com \
--cc=roszenrami@gmail.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).