From: Olivier MATZ <olivier.matz@6wind.com>
To: "Simon Kågström" <simon.kagstrom@netinsight.net>, dev@dpdk.org
Subject: Re: [dpdk-dev] build issue with out-of-tree builds and multiple mounts
Date: Mon, 04 May 2015 14:48:20 +0200 [thread overview]
Message-ID: <55476A94.5000809@6wind.com> (raw)
In-Reply-To: <55476941.3030202@netinsight.net>
Hi Simon,
On 05/04/2015 02:42 PM, Simon Kågström wrote:
> Hi!
>
> I'm trying to do a out-of-tree build of DPDK 2.0.0 (with make -C and
> O=), but failing with errors such as
>
> In file included from
> [...]/lib/librte_eal/common/include/rte_eal_memconfig.h:40:0,
> [...]
> rte_malloc_heap.h:39:26: fatal error: rte_spinlock.h: No such file or
> directory
>
> Looking in the include/ directory in my build directory, I see a lot of
> invalid symlinks to things like rte_spinlock.h:
>
> lrwxrwxrwx 1 ska users 99 May 4 14:33 rte_spinlock.h ->
> ../[...]/dpdk/lib/librte_eal/common/include/arch/x86/rte_spinlock.h
Can you please send the full make command line that produces this
issue?
Thanks,
Olivier
>
> and I believe that this is caused by my use of multiple mounts: I have
> my home directory and the source code on NFS, while the build directory
> is on local disk (under a build/-symlink from my home directory). So
> using ../ relative to the build directory will actually end up on the
> local disk, and not work.
>
>
> I guess it should be possible to workaround this by building somewhere
> else, but perhaps there is some patch to be made in mk/? Any pointer to
> where to look?
>
> // Simon
>
next prev parent reply other threads:[~2015-05-04 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 12:42 Simon Kågström
2015-05-04 12:48 ` Olivier MATZ [this message]
2015-05-04 12:55 ` Simon Kågström
2015-05-05 9:00 ` [dpdk-dev] [PATCH] scripts: fix relpath.sh output when build dir is a symlink Olivier Matz
2015-05-05 9:00 ` Olivier MATZ
2015-05-05 9:14 ` Simon Kågström
2015-05-12 12:26 ` Thomas Monjalon
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=55476A94.5000809@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=simon.kagstrom@netinsight.net \
/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).