From: Thomas Monjalon <thomas@monjalon.net>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: dev@dpdk.org, Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>,
"nd@arm.com" <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v1] doc: update Linux gsg for ARM64 cross compile
Date: Wed, 05 Jun 2019 12:34:26 +0200 [thread overview]
Message-ID: <2308425.KpECZWGM36@xps> (raw)
In-Reply-To: <BYAPR18MB2424F7908EE3E7F8782456BEC8150@BYAPR18MB2424.namprd18.prod.outlook.com>
> > libnuma.so is needed to augment the cross toolchain with NUMA support.
> > This fixed meson cross compiling issue.
> >
> > Command used:
> > meson arm64-build --cross-file config/arm/arm64_armv8_linux_gcc ninja -C
> > arm64-build
> >
> > Compiling error:
> > .../aarch64-linux-gnu/bin/ld: lib/librte_eal.so.10.1: version node not found
> > for symbol numa_run_on_node_mask@@libnuma_1.2
> > .../aarch64-linux-gnu/bin/ld: failed to set dynamic section sizes:
> > Bad value
> > collect2: error: ld returned 1 exit status [58/1370] Compiling C object
> > 'lib/76b5a35@@rte_cmdline@sta/ librte_cmdline_cmdline_parse_string.c.o'.
> > ninja: build stopped: subcommand failed.
> >
> > Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> > Reviewed-by: Gavin Hu <gavin.hu@arm.com>
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied with following lines for backport:
Fixes: 01add9da25cd ("doc: add cross compiling guide")
Cc: stable@dpdk.org
prev parent reply other threads:[~2019-06-05 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 8:41 Ruifeng Wang
2019-05-15 8:41 ` Ruifeng Wang
2019-06-04 14:43 ` Jerin Jacob Kollanukkaran
2019-06-05 10:34 ` Thomas Monjalon [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=2308425.KpECZWGM36@xps \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@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).