From: Thomas Monjalon <thomas@monjalon.net>
To: Gabriel Danjon <gabriel.danjon@cybertestsystems.com.sg>
Cc: users@dpdk.org,
Alexis DANJON <alexis.danjon@cybertestsystems.com.sg>,
Laurent CHABENET <laurent.chabenet@cybertestsystems.com.sg>,
Antoine LORIN <antoine.lorin@cybertestsystems.com.sg>,
"gregory.fresnais@cybertestsystems.com.sg"
<gregory.fresnais@cybertestsystems.com.sg>,
Julien RAMET <julien.ramet@cybertestsystems.com.sg>
Subject: Re: [dpdk-users] Enable to install DPDK on Centos 8-Stream
Date: Thu, 27 May 2021 19:18:15 +0200 [thread overview]
Message-ID: <8407135.z5SgJNz3Zo@thomas> (raw)
In-Reply-To: <bb4f60b9-709b-43c9-2399-2e8b72381cc0@cybertestsystems.com.sg>
27/05/2021 18:10, Gabriel Danjon:
> Hello,
>
> I am having difficulties to compile and install DPDK from sources on the
> latest Centos 8-Stream.
Did you compile and install DPDK successfully?
Where is it installed?
>
> After having installed the required drivers and libraries, following the
> documentation and the DPDK build (meson build && cd build && ninja &&
> ninja install && ldconfig), I tried to compile the helloworld example
> without success:
> 'Makefile:12: *** "no installation of DPDK found". Stop.'
>
>
> Please find attached to this mail some logs.
The log is way too long to be read.
Please copy only what is relevant.
> Could you provide help please ?
It looks to be basic issue with library installation.
Did you read the doc?
http://doc.dpdk.org/guides/linux_gsg/build_dpdk.html
Especially this note:
"
On some linux distributions, such as Fedora or Redhat, paths in /usr/local are not in the default paths for the loader. Therefore, on these distributions, /usr/local/lib and /usr/local/lib64 should be added to a file in /etc/ld.so.conf.d/ before running ldconfig.
"
prev parent reply other threads:[~2021-05-27 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 16:10 Gabriel Danjon
2021-05-27 17:18 ` Thomas Monjalon [this message]
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=8407135.z5SgJNz3Zo@thomas \
--to=thomas@monjalon.net \
--cc=alexis.danjon@cybertestsystems.com.sg \
--cc=antoine.lorin@cybertestsystems.com.sg \
--cc=gabriel.danjon@cybertestsystems.com.sg \
--cc=gregory.fresnais@cybertestsystems.com.sg \
--cc=julien.ramet@cybertestsystems.com.sg \
--cc=laurent.chabenet@cybertestsystems.com.sg \
--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).