From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] build: fix EAL path to drivers for static builds
Date: Mon, 23 Oct 2017 11:32:40 +0100 [thread overview]
Message-ID: <20171023103239.GA28468@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <20171017164102.71159-1-bruce.richardson@intel.com>
On Tue, Oct 17, 2017 at 05:41:02PM +0100, Bruce Richardson wrote:
> For static builds, even though the drivers are installed in the lib folder
> that does not mean that that folder should be set as the EAL driver search
> path. If it is, EAL will try loading all shared libraries as drivers and
> fail to start. Instead, track the EAL driver path separately from the
> driver install path, allowing static builds to have an empty driver path
> by default.
>
> Fixes: d8b85d98b3f7 ("build: add initial infrastructure for meson & ninja builds")
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>
> ----
> NOTE: on apply will be merged into offending commit in next-build tree.
> ---
> config/meson.build | 3 +--
> meson.build | 2 ++
> 2 files changed, 3 insertions(+), 2 deletions(-)
Applied and squashed to commit on dpdk-next-build
/Bruce
prev parent reply other threads:[~2017-10-23 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 16:41 Bruce Richardson
2017-10-23 10:32 ` Bruce Richardson [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=20171023103239.GA28468@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@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).