From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"jerinjacobk@gmail.com" <jerinjacobk@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>
Subject: RE: [PATCH v2 3/4] doc: arm64 cross build numactl compilers
Date: Wed, 15 Dec 2021 08:38:09 +0000 [thread overview]
Message-ID: <AS8PR08MB70800F9B6679727D211BD4AA9E769@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <1638875109-5544-4-git-send-email-juraj.linkes@pantheon.tech>
> -----Original Message-----
> From: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Sent: Tuesday, December 7, 2021 7:05 PM
> To: thomas@monjalon.net; david.marchand@redhat.com; Honnappa
> Nagarahalli <Honnappa.Nagarahalli@arm.com>; Ruifeng Wang
> <Ruifeng.Wang@arm.com>; ferruh.yigit@intel.com; jerinjacobk@gmail.com
> Cc: dev@dpdk.org; Juraj Linkeš <juraj.linkes@pantheon.tech>
> Subject: [PATCH v2 3/4] doc: arm64 cross build numactl compilers
>
> Numactl cross compilation doesn't work with clang, remove it and fix the gcc
> cross compiler executable name.
>
> Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> ---
> doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
> b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
> index af159bbf93..6153bc5b77 100644
> --- a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
> +++ b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
> @@ -35,13 +35,14 @@ NUMA is required by most modern machines, not
> needed for non-NUMA architectures.
> git checkout v2.0.13 -b v2.0.13
> ./autogen.sh
> autoconf -i
> - ./configure --host=aarch64-linux-gnu CC=<compiler> --prefix=<numa
> install dir>
> + ./configure --host=aarch64-linux-gnu CC=aarch64-none-linux-gnu-gcc
> + --prefix=<numa install dir>
> make install
>
> .. note::
>
> - The compiler above can be either aarch64-linux-gnu-gcc or clang.
> - See below for information on how to get specific compilers.
> + The compiler is aarch64-none-linux-gnu-gcc if you download gcc using the
> + below guide. If you're using a different compiler, make sure you're using
> + the proper executable name.
>
> The numa header files and lib file is generated in the include and lib folder
> respectively under ``<numa install dir>``.
> --
> 2.20.1
Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
next prev parent reply other threads:[~2021-12-15 8:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 10:00 [PATCH v1] doc: arm64 cross docs improvements/fixes Juraj Linkeš
2021-11-26 13:53 ` Thomas Monjalon
2021-11-26 14:17 ` Juraj Linkeš
2021-12-07 11:05 ` [PATCH v2 0/4] " Juraj Linkeš
2021-12-07 11:05 ` [PATCH v2 1/4] doc: arm64 cross build CFLAGS/LDFLAGS alternatives Juraj Linkeš
2021-12-15 8:00 ` Ruifeng Wang
2021-12-07 11:05 ` [PATCH v2 2/4] doc: arm64 cross build binary names update Juraj Linkeš
2021-12-15 8:02 ` Ruifeng Wang
2021-12-07 11:05 ` [PATCH v2 3/4] doc: arm64 cross build numactl compilers Juraj Linkeš
2021-12-15 8:38 ` Ruifeng Wang [this message]
2021-12-07 11:05 ` [PATCH v2 4/4] docs: add an example arm64 cross file Juraj Linkeš
2021-12-15 8:59 ` Ruifeng Wang
2022-01-25 13:19 ` [PATCH v3 0/4] arm64 cross docs improvements/fixes Juraj Linkeš
2022-01-25 13:19 ` [PATCH v3 1/4] doc: arm64 cross build CFLAGS/LDFLAGS alternatives Juraj Linkeš
2022-01-25 13:20 ` [PATCH v3 2/4] doc: arm64 cross build binary names update Juraj Linkeš
2022-01-25 13:20 ` [PATCH v3 3/4] doc: arm64 cross build numactl compilers Juraj Linkeš
2022-01-25 13:20 ` [PATCH v3 4/4] doc: add an example arm64 cross file Juraj Linkeš
2022-03-16 19:19 ` [PATCH v3 0/4] arm64 cross docs improvements/fixes 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=AS8PR08MB70800F9B6679727D211BD4AA9E769@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=thomas@monjalon.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).