From: "Ginés García Avilés" <gines.garcia@i2cat.net>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] SW Turbo Poll Mode Driver
Date: Tue, 5 Oct 2021 09:02:43 +0200 [thread overview]
Message-ID: <CAFggs4OyVz3-0zBHr5AY5LGzV1Pusb6SJcxHzDGb-wc9YbKC5g@mail.gmail.com> (raw)
In-Reply-To: <BY5PR11MB4451DD3903411397FCB7C977F8AE9@BY5PR11MB4451.namprd11.prod.outlook.com>
Hi Nicolas,
thanks a lot for your help.
However, with the latest version of DPDK I'm still facing the following
issue:
- "drivers/baseband/turbo_sw/meson.build:13:4: ERROR: C library
'libstdc++' not found"
These are the steps I'm actually following for the whole process:
- Set env vars (*ICC *compiler, FLEXRAN_SDK, DIR_WIRELESS_SDK, ...)
- meson x86_64-native-linux-icc
- cd x86_64-native-linux-icc
- meson configure -Dflexran_sdk=xxx/build-avx512-icc/install
- ninja
Thanks in advance,
Ginés.
El lun, 4 oct 2021 a las 23:05, Chautru, Nicolas (<nicolas.chautru@intel.com>)
escribió:
> Hi Gines,
> The only thing is to make sure to set the meson option to point to the
> right location
> See https://doc.dpdk.org/guides/bbdevs/turbo_sw.html : for instance
> something like this "meson configure
> -Dflexran_sdk=xxx/build-avx512-icc/install"
> Then meson build framework will just link the libraries: see
> drivers\baseband\turbo_sw\meson.build which uses cc.find_library to
> dynamically find and link the libraries
>
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Wednesday, September 29, 2021 3:41 AM
> > To: Ginés García Avilés <gines.garcia@i2cat.net>
> > Cc: users@dpdk.org; Chautru, Nicolas <nicolas.chautru@intel.com>
> > Subject: Re: [dpdk-users] SW Turbo Poll Mode Driver
> >
> > +Cc maintainer
> >
> > 14/09/2021 12:58, Ginés García Avilés:
> > > Hi all,
> > > After following the steps listed here (3. SW Turbo Poll Mode Driver —
> > > Data Plane Development Kit 21.08.0 documentation (dpdk.org)
> > > <http://doc.dpdk.org/guides/bbdevs/turbo_sw.html#>), using the
> > > specific versions of DPDK and FlexRAN, I'm facing an error while
> > > trying to run one of the bbdev
> > > tests:
> > > - command:
> > > > python2 test-bbdev.py
> > > -e="--vdev=baseband_turbo_sw,socket_id=0,max_nb_queues=8" -c
> > > validation -v turbo_dec_default.data
> > > - Error:
> > > > "Device 0 (baseband_turbo_sw) does not support specified
> > capabilities"
> > >
> > > which I think is due to an incorrect linkage of DPDK and FlexRAN. I
> > > have checked all the environmental variables pointing to the different
> > > components and everything seems to be correct.
> > >
> > > Any suggestions about how to solve this problem?
> > >
> > > Thanks a lot for your help,
> > > Ginés.
> >
> >
>
>
next prev parent reply other threads:[~2021-10-05 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 10:58 Ginés García Avilés
2021-09-29 10:41 ` Thomas Monjalon
2021-10-04 21:05 ` Chautru, Nicolas
2021-10-05 7:02 ` Ginés García Avilés [this message]
2021-10-05 20:56 ` Chautru, Nicolas
2021-10-13 15:30 ` Ginés García Avilés
2021-10-19 9:02 ` Ginés García Avilés
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=CAFggs4OyVz3-0zBHr5AY5LGzV1Pusb6SJcxHzDGb-wc9YbKC5g@mail.gmail.com \
--to=gines.garcia@i2cat.net \
--cc=nicolas.chautru@intel.com \
--cc=thomas@monjalon.net \
--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).