From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Gavin Hu <gavin.hu@arm.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v5 2/2] doc: add a guide doc for cross compiling from x86
Date: Thu, 31 May 2018 01:05:35 +0530 [thread overview]
Message-ID: <20180530193534.GA1336@jerin> (raw)
In-Reply-To: <1527590616-28299-3-git-send-email-gavin.hu@arm.com>
-----Original Message-----
> Date: Tue, 29 May 2018 18:43:36 +0800
> From: Gavin Hu <gavin.hu@arm.com>
> To: dev@dpdk.org
> CC: gavin.hu@arm.com
> Subject: [dpdk-dev] [PATCH v5 2/2] doc: add a guide doc for cross compiling
> from x86
> X-Mailer: git-send-email 2.1.4
>
> + 1. EXTRA_CFLAGS and EXTRA_LDFLAGS should be added to include the NUMA headers and link the library respectively,
> + if the step :ref:`argment_the_cross_toolcain_with_numa_support` was skipped therefore the toolchain was not
> + argmented with NUMA support.
> +
> + 2. RTE_DEVEL_BUILD has to be disabled, otherwise the numa.h file gets
If the warnings are from numa.h then please use -isystem <numa install dir> instead of disabling RTE_DEVEL_BUILD.
> + a lot of compiling errors of Werror=cast-qual, Werror=strict-prototypes and Werror=old-style-definition.
> + An example is given below:
> +
> + .. code-block:: console
> +
> + make -j CROSS=aarch64-linux-gnu- CONFIG_RTE_KNI_KMOD=n CONFIG_RTE_EAL_IGB_UIO=n
> + RTE_DEVEL_BUILD=n EXTRA_CFLAGS="-I<numa_install_dir>/include" EXTRA_LDFLAGS=
> + "-L<numa_install_dir>/lib -lnuma"
> +
As discussed earlier, meson cross build instruction is missing.
> diff --git a/doc/guides/linux_gsg/index.rst b/doc/guides/linux_gsg/index.rst
> index 2a7bdfe..077f930 100644
> --- a/doc/guides/linux_gsg/index.rst
> +++ b/doc/guides/linux_gsg/index.rst
> @@ -13,6 +13,7 @@ Getting Started Guide for Linux
> intro
> sys_reqs
> build_dpdk
> + cross_build_dpdk_for_arm64
> linux_drivers
> build_sample_apps
> enable_func
> --
> 2.1.4
>
next prev parent reply other threads:[~2018-05-30 19:35 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 3:38 [dpdk-dev] [PATCH 0/2] *** gcc cross compile dpdk *** Gavin Hu
2018-05-24 3:38 ` [dpdk-dev] [PATCH 1/2] mk: fix cross build errors Gavin Hu
2018-05-24 13:46 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2018-05-25 7:53 ` Gavin Hu
2018-05-24 3:38 ` [dpdk-dev] [PATCH 2/2] doc: add a guide doc for cross compiling from x86 Gavin Hu
2018-05-24 10:45 ` Kovacevic, Marko
2018-05-24 10:47 ` Kovacevic, Marko
2018-05-24 11:17 ` Jerin Jacob
2018-05-24 13:20 ` Bruce Richardson
2018-05-25 7:00 ` Gavin Hu
2018-05-24 13:54 ` Thomas Monjalon
2018-05-24 17:16 ` Jerin Jacob
2018-05-24 20:31 ` Thomas Monjalon
2018-05-28 6:53 ` [dpdk-dev] [PATCH v2 1/2] mk: fix cross build errors Gavin Hu
2018-05-28 6:53 ` [dpdk-dev] [PATCH v2 2/2] doc: add a guide doc for cross compiling from x86 Gavin Hu
2018-05-28 13:25 ` Bruce Richardson
2018-05-29 1:24 ` Gavin Hu
2018-05-28 16:01 ` Kovacevic, Marko
2018-05-28 13:24 ` [dpdk-dev] [PATCH v2 1/2] mk: fix cross build errors Bruce Richardson
2018-05-29 1:22 ` Gavin Hu
2018-05-29 14:45 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2018-05-29 15:00 ` Bruce Richardson
2018-05-29 16:20 ` Gavin Hu
2018-05-29 19:53 ` Thomas Monjalon
2018-05-29 6:51 ` [dpdk-dev] [PATCH v3 " Gavin Hu
2018-05-29 6:51 ` [dpdk-dev] [PATCH v3 2/2] doc: add a guide doc for cross compiling from x86 Gavin Hu
2018-05-29 7:21 ` [dpdk-dev] [PATCH v4 0/2] *** cross gcc fix and guide doc *** Gavin Hu
2018-05-29 7:21 ` [dpdk-dev] [PATCH v4 1/2] mk: fix cross build errors Gavin Hu
2018-05-29 7:21 ` [dpdk-dev] [PATCH v4 2/2] doc: add a guide doc for cross compiling from x86 Gavin Hu
2018-05-29 8:39 ` Kovacevic, Marko
2018-05-29 10:43 ` [dpdk-dev] [PATCH v5 0/2] *** cross gcc compile fix and add a guide doc *** Gavin Hu
2018-05-29 10:43 ` [dpdk-dev] [PATCH v5 1/2] mk: fix cross build errors Gavin Hu
2018-05-29 15:09 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2018-05-29 10:43 ` [dpdk-dev] [PATCH v5 2/2] doc: add a guide doc for cross compiling from x86 Gavin Hu
2018-05-29 13:33 ` Kovacevic, Marko
2018-05-30 19:16 ` Thomas Monjalon
2018-05-30 19:35 ` Jerin Jacob [this message]
2018-06-04 6:03 ` Gavin Hu
2018-06-04 12:50 ` Jerin Jacob
2018-06-12 1:27 ` Gavin Hu
2018-06-12 12:06 ` Gavin Hu
2018-06-12 12:11 ` Thomas Monjalon
2018-06-14 9:51 ` [dpdk-dev] [PATCH v6 0/7] *** fix the cross compile errors *** Gavin Hu
2018-06-14 9:51 ` [dpdk-dev] [PATCH v6 1/7] mk: fix cross build errors Gavin Hu
2018-06-14 9:51 ` [dpdk-dev] [PATCH v6 2/7] doc: add a guide doc for cross compiling from x86 Gavin Hu
2018-06-14 9:51 ` [dpdk-dev] [PATCH v6 3/7] devtools: fix the Exec format error Gavin Hu
2018-06-14 10:34 ` Bruce Richardson
2018-06-15 8:07 ` Gavin Hu
2018-06-14 9:51 ` [dpdk-dev] [PATCH v6 4/7] build: fix the meson build warning Gavin Hu
2018-06-14 10:34 ` Bruce Richardson
2018-06-14 9:51 ` [dpdk-dev] [PATCH v6 5/7] devtools: fix the missing ninja command error on CentOS Gavin Hu
2018-06-14 10:40 ` Bruce Richardson
2018-06-15 8:08 ` Gavin Hu
2018-06-14 9:51 ` [dpdk-dev] [PATCH v6 6/7] build: fix the meson cross compile error Gavin Hu
2018-06-14 10:42 ` Bruce Richardson
2018-06-14 9:51 ` [dpdk-dev] [PATCH v6 7/7] devtools: expand meson cross compiling coverage Gavin Hu
2018-06-14 10:45 ` Bruce Richardson
2018-06-15 8:09 ` Gavin Hu
2018-06-15 10:23 ` Gavin Hu
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=20180530193534.GA1336@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.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).