DPDK usage discussions
 help / color / mirror / Atom feed
From: Chris Paquin <cpaquin@redhat.com>
To: RICCARDO RUSSO <riccardo.russo79@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Install DPDK on Centos7
Date: Fri, 20 Apr 2018 16:26:35 +0000	[thread overview]
Message-ID: <CAAMYPe6zKziOZXzzCKGDgVZPZHJnUYsOqmDpemB40zi9W0kuWw@mail.gmail.com> (raw)
In-Reply-To: <CAAbvOZR6N5yCgr-rseMsxG9z8w2KMqetX1=1pcH4Q=73hj=pqw@mail.gmail.com>

Here are my notes from the rhel, might be helpful.

https://fatmin.com/2017/08/25/how-to-install-testpmd-on-rhel-7-x/


On Fri, Apr 20, 2018, 12:02 PM RICCARDO RUSSO <riccardo.russo79@gmail.com>
wrote:

> Hello,
> I'm trying to install dpdk on CentOS
>
> $ yum -y update
> $ yum -y install git gcc numactl-devel libpcap-devel kernel-devel
> $ hostnamectl
> ...
>     Virtualization: kvm
>   Operating System: CentOS Linux 7 (Core)
>        CPE OS Name: cpe:/o:centos:centos:7
>             Kernel: Linux 3.10.0-514.26.1.el7.x86_64
>       Architecture: x86-64
>
> $ wget
> http://dpdk.org/browse/dpdk-stable/snapshot/dpdk-stable-18.02.tar.gz
> $ gunzip dpdk-stable-18.02.tar.gz
> $ tar -xvf dpdk-stable-18.02.tar
> $ export RTE_SDK=/root/dpdk-stable-18.02
> $ export RTE_TARGET=x86_64-native-linuxapp-gcc
> $ cd $RTE_SDK
> $ make install T=x86_64-native-linuxapp-gcc DESTDIR=install
> ...
> == Build lib/librte_eal/linuxapp/eal
>   SYMLINK-FILE include/exec-env/rte_kni_common.h
>   CC eal.o
>   CC eal_hugepage_info.o
>   CC eal_memory.o
>   CC eal_thread.o
>   CC eal_log.o
>   CC eal_vfio.o
>   CC eal_vfio_mp_sync.o
>   CC eal_debug.o
>   CC eal_lcore.o
>   CC eal_timer.o
>   CC eal_interrupts.o
>   CC eal_alarm.o
>   CC eal_common_lcore.o
>   CC eal_common_timer.o
>   CC eal_common_memzone.o
>   CC eal_common_log.o
>   CC eal_common_launch.o
>   CC eal_common_memory.o
>   CC eal_common_tailqs.o
>   CC eal_common_errno.o
>   CC eal_common_cpuflags.o
>   CC eal_common_hypervisor.o
>   CC eal_common_string_fns.o
>   CC eal_common_hexdump.o
>   CC eal_common_devargs.o
>   CC eal_common_bus.o
>   CC eal_common_dev.o
>   CC eal_common_options.o
>   CC eal_common_thread.o
>   CC eal_common_proc.o
>   CC rte_malloc.o
>   CC malloc_elem.o
>   CC malloc_heap.o
>   CC rte_keepalive.o
>   CC rte_service.o
>   CC rte_reciprocal.o
>   CC rte_cpuflags.o
>   CC rte_hypervisor.o
>   CC rte_spinlock.o
>   CC rte_cycles.o
>   AR librte_eal.a
>   INSTALL-LIB librte_eal.a
> == Build lib/librte_eal/linuxapp/igb_uio
> make: *** /lib/modules/3.10.0-514.26.1.el7.x86_64/build: No such file or
> directory.  Stop.
> make[7]: *** [igb_uio.ko] Error 2
> make[6]: *** [igb_uio] Error 2
> make[5]: *** [linuxapp] Error 2
> make[4]: *** [librte_eal] Error 2
> make[3]: *** [lib] Error 2
> make[2]: *** [all] Error 2
> make[1]: *** [pre_install] Error 2
> make: *** [install] Error 2
>
> I don't know what I am missing
> Rr
>

  reply	other threads:[~2018-04-20 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 16:01 RICCARDO RUSSO
2018-04-20 16:26 ` Chris Paquin [this message]
2018-04-22 18:15   ` ..
2018-04-23  7:27 ` James Bensley
2018-04-23 14:11   ` Chris Paquin

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=CAAMYPe6zKziOZXzzCKGDgVZPZHJnUYsOqmDpemB40zi9W0kuWw@mail.gmail.com \
    --to=cpaquin@redhat.com \
    --cc=riccardo.russo79@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).