From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Tomasz Duszynski <tdu@semihalf.com>, dev@dpdk.org
Cc: mw@semihalf.com, dima@marvell.com, nsamsono@marvell.com,
Jianbo.liu@linaro.org
Subject: Re: [dpdk-dev] [PATCH] net/mrvl: update MUSDK library build instructions
Date: Fri, 26 Jan 2018 16:37:27 +0000 [thread overview]
Message-ID: <672fc2c9-cf19-02ee-59a3-f06903fd6307@intel.com> (raw)
In-Reply-To: <1516953745-26545-1-git-send-email-tdu@semihalf.com>
On 1/26/2018 8:02 AM, Tomasz Duszynski wrote:
> By default both static and shared libraries should be created while
> building MUSDK library. It turns out that this will not happen if
> host parameter is not explicitly passed to the configure script.
>
> Specifying host makes sure configure will detect support for shared
> libraries.
>
> Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
> ---
> doc/guides/nics/mrvl.rst | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/doc/guides/nics/mrvl.rst b/doc/guides/nics/mrvl.rst
> index 892097d..77b2d66 100644
> --- a/doc/guides/nics/mrvl.rst
> +++ b/doc/guides/nics/mrvl.rst
> @@ -221,14 +221,13 @@ Usage example
> Building DPDK
> -------------
>
> -Driver needs precompiled MUSDK library during compilation. Please consult
> -``doc/musdk_get_started.txt`` for the detailed build instructions.
> +Driver needs precompiled MUSDK library during compilation.
>
> .. code-block:: console
>
> export CROSS_COMPILE=<toolchain>/bin/aarch64-linux-gnu-
> ./bootstrap
> - ./configure --enable-bpool-dma=64
> + ./configure --host=aarch64-linux-gnu --enable-bpool-dma=64
One more flag is required for crypto PMD, right? Is it documented somewhere?
> make install
>
> MUSDK will be installed to `usr/local` under current directory.
>
next prev parent reply other threads:[~2018-01-26 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 8:02 Tomasz Duszynski
2018-01-26 16:37 ` Ferruh Yigit [this message]
2018-01-26 16:46 ` Tomasz Duszynski
2018-01-26 17:18 ` Ferruh Yigit
2018-01-26 18:14 ` Ferruh Yigit
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=672fc2c9-cf19-02ee-59a3-f06903fd6307@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Jianbo.liu@linaro.org \
--cc=dev@dpdk.org \
--cc=dima@marvell.com \
--cc=mw@semihalf.com \
--cc=nsamsono@marvell.com \
--cc=tdu@semihalf.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).