DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marc Sune <marc.sune@bisdn.de>
To: Thomas Monjalon <thomas.monjalon@6wind.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] Unable to compile DPDK 1.5 on Debian GNU/Linux: lib/librte_eal/linuxapp/igb_uio
Date: Tue, 05 Nov 2013 16:50:13 +0100	[thread overview]
Message-ID: <527913B5.60702@bisdn.de> (raw)
In-Reply-To: <20131105154236.GJ26200@debian>

Dear Thomas,

Thank you that really was the problem. I am still puzzled why it 
happend, since the headers were installed before. I will update the rest 
of installations.

Probably it would be slightly better to check whether the build folder 
contains the right Makefiles and scripts needed to print the right 
error, otherwise the output of make is misleading.

As I said thank you and regards
marc

On 05/11/13 16:42, Cyril Cressent wrote:
> Hi Marc,
>
> On Mon, Nov 04, 2013 at 09:53:29PM +0100, Marc Sune wrote:
>> 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).
> build should be a symlink to the corresponding kernel sources or
> headers, usually in /usr/src/.
>
>> 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 ..
> That output shows that "build" is not a symlink to the kernel
> sources/headers. Make it a symlink to /usr/src/linux-headers-`uname -r`.
> And double check you have the kernel headers there...
>
>> 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.
> That's weird ; you should have had the symlink properly created if you
> used apt...
>
>> 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..
> Yes, the target folder is /lib/modules/`uname -r`/build, which contains
> a Makefile. Yours is empty because it's not the expected symlink, and
> make then complains because there is no Makefile there.

      reply	other threads:[~2013-11-05 15:49 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
2013-11-05 15:42     ` Cyril Cressent
2013-11-05 15:50       ` Marc Sune [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=527913B5.60702@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).