DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marc Sune <marc.sune@bisdn.de>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Unable to compile DPDK 1.5 on Debian GNU/Linux: lib/librte_eal/linuxapp/igb_uio
Date: Mon, 04 Nov 2013 21:53:29 +0100	[thread overview]
Message-ID: <52780949.1020706@bisdn.de> (raw)
In-Reply-To: <2616151.R1XFxBmKnN@x220>

Dear Thomas, all,

I think it is not this variable. When the folder /lib/modules/$(shell 
uname -r)/build does not exist, the Makefile properly warns you (I 
manually created it, since it was not existing during the first 
compilation attempt).

marc@bisdn-dev:~/BISDN/dpdk$ grep RTE_KERNELDIR * -R
mk/rte.vars.mk:115:RTE_KERNELDIR ?= /lib/modules/$(shell uname -r)/build
mk/rte.module.mk:80:    @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) 
O=$(RTE_KERNELDIR)
mk/rte.module.mk:90:    @$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) 
O=$(RTE_KERNELDIR) \
mk/rte.module.mk:100:    $(Q)$(MAKE) -C $(RTE_KERNELDIR) M=$(CURDIR) 
O=$(RTE_KERNELDIR) clean
marc@bisdn-dev:~/BISDN/dpdk$ ls /lib/modules/`uname -r`/build
marc@bisdn-dev:~/BISDN/dpdk$ ls /lib/modules/`uname -r`/
build   modules.alias      modules.builtin      modules.dep 
modules.devname  modules.softdep  modules.symbols.bin
kernel  modules.alias.bin  modules.builtin.bin  modules.dep.bin 
modules.order    modules.symbols  source
marc@bisdn-dev:~/BISDN/dpdk$ ls /lib/modules/`uname -r`/build -la
total 8
drwxr-xr-x 2 root root 4096 jul 31 16:41 .
drwxr-xr-x 4 root root 4096 nov  4 16:43 ..

Concerning kernel headers, the kernel headers for the running kernel 
were already installed (via apt-get install linux-headers-`uname -r`), 
and no custom kernel is installed in the system.

Actually, this seems to me more of a variable definition problem, like 
the $(wildcard $(RTE_KERNELDIR)) but somehow related to the DPDK target 
folders, rather than an issue with the headers/gcc, since it is 'make' 
which is not able to find the existing file. But I could be wrong..

Any (more) ideas?

thanks and regards
marc

On 04/11/13 19:06, Thomas Monjalon wrote:
> 04/11/2013 13:58, Marc Sune :
>> I am unable to compile DPDK 1.5 (and previous versions) on Debian
>> GNU/Linux Wheezy (7) and Squeeze (6).
>>
>> == Build lib/librte_eal/linuxapp/igb_uio
>> make[8]: *** No targets specified and no makefile found.  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]: *** [x86_64-default-linuxapp-gcc_install] Error 2
>> make: *** [install] Error 2
> You probably don't have linux headers installed.
> We probably should check $(wildcard $(RTE_KERNELDIR)) in order to provide an
> error message.
> Do not hesitate to provide a patch for mk/rte.module.mk.
>

  reply	other threads:[~2013-11-04 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 12:58 Marc Sune
2013-11-04 14:21 ` Cyril Cressent
2013-11-04 14:48   ` Marc Sune
2013-11-04 15:02     ` Wiles, Roger Keith
2013-11-04 15:14       ` Marc Sune
2013-11-04 15:35 ` Cyril Cressent
2013-11-04 18:06 ` Thomas Monjalon
2013-11-04 20:53   ` Marc Sune [this message]
2013-11-05 15:42     ` Cyril Cressent
2013-11-05 15:50       ` Marc Sune

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=52780949.1020706@bisdn.de \
    --to=marc.sune@bisdn.de \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    /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).