From: Tom Barbette <tom.barbette@uclouvain.be>
To: Nigel Kukard <nkukard@LBSD.net>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: DPDK 21.08 build failure with meson 0.60.0
Date: Wed, 27 Oct 2021 12:43:00 +0200 [thread overview]
Message-ID: <fecac024-5278-9bd6-85c3-659240789bc0@uclouvain.be> (raw)
In-Reply-To: <ea4eb70f-5da1-2690-c9f9-3be3e144ab05@LBSD.net>
[-- Attachment #1: Type: text/plain, Size: 3513 bytes --]
I got that too :) No solution though...
Le 26-10-21 à 07:31, Nigel Kukard a écrit :
>
> I'm wondering if anyone can help me figure out why this is happening?
> it looks like it was when meson was upgraded to 0.60.0.
>
> I'm building on Arch Linux, with rdma-core 37.0 already installed
> (custom built).
>
> Here is my build commands for rdma-core (no problem)...
>
> mkdir -p build
> cd build
> cmake \
> -GNinja \
> -DENABLE_VALGRIND=0 \
> -DCMAKE_BUILD_TYPE='Release' \
> -DCMAKE_INSTALL_PREFIX='/usr' \
> -DCMAKE_INSTALL_RUNDIR='/run' \
> -DCMAKE_INSTALL_SBINDIR='/usr/bin' \
> -DCMAKE_INSTALL_LIBDIR='/usr/lib' \
> -DCMAKE_INSTALL_LIBEXECDIR='/usr/lib/rdma' \
> -DCMAKE_INSTALL_SYSCONFDIR='/etc' \
> -DCMAKE_INSTALL_PERLDIR='/usr/share/perl5/vendor_perl' \
> ..
> ninja
>
>
> Here is my build command for dpdk...
>
> meson -Dplatform=generic -Dexamples=all build --prefix=/usr
> ninja -C build
>
> gcc 11.1.0
>
> meson 0.60.0
>
> [504/2980] Compiling C object lib/librte_node.a.p/node_null.c.o
> [505/2980] Compiling C object lib/librte_node.a.p/node_log.c.o
> [506/2980] Compiling C object
> drivers/libtmp_rte_common_cpt.a.p/common_cpt_cpt_fpm_tables.c.o
> [507/2980] Compiling C object lib/librte_node.a.p/node_ip4_rewrite.c.o
> [508/2980] Generating drivers/rte_common_cpt_def with a custom command
> [509/2980] Generating drivers/rte_common_cpt_mingw with a custom command
> [510/2980] Compiling C object
> drivers/libtmp_rte_common_cpt.a.p/common_cpt_cpt_pmd_ops_helper.c.o
> [511/2980] Compiling C object
> drivers/libtmp_rte_common_dpaax.a.p/common_dpaax_dpaax_iova_table.c.o
> [512/2980] Linking static target drivers/libtmp_rte_common_cpt.a
> [513/2980] Generating drivers/rte_common_cpt.pmd.c with a custom command
> FAILED: drivers/rte_common_cpt.pmd.c
> /usr/bin/python ../buildtools/gen-pmdinfo-cfile.py
> /build/dpdk/src/dpdk-21.08/build/buildtools ar
> /build/dpdk/src/dpdk-21.08/build/drivers/libtmp_rte_common_cpt.a
> drivers/rte_common_cpt.pmd
> .c /usr/bin/python ../buildtools/pmdinfogen.py elf
> ar: `x' cannot be used on thin archives.
> Traceback (most recent call last):
> File
> "/build/dpdk/src/dpdk-21.08/build/../buildtools/gen-pmdinfo-cfile.py",
> line 17, in <module>
> run_ar("x")
> File
> "/build/dpdk/src/dpdk-21.08/build/../buildtools/gen-pmdinfo-cfile.py",
> line 12, in <lambda>
> run_ar = lambda command: subprocess.run(
> File "/usr/lib/python3.9/subprocess.py", line 528, in run
> raise CalledProcessError(retcode, process.args,
> subprocess.CalledProcessError: Command '['ar', 'x',
> '/build/dpdk/src/dpdk-21.08/build/drivers/libtmp_rte_common_cpt.a']'
> returned non-zero exit status 1.
> [514/2980] Compiling C object
> drivers/libtmp_rte_common_dpaax.a.p/common_dpaax_caamflib.c.o
> [515/2980] Compiling C object lib/librte_node.a.p/node_pkt_cls.c.o
> [516/2980] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
> [517/2980] Compiling C object
> lib/librte_pipeline.a.p/pipeline_rte_table_action.c.o
> [518/2980] Compiling C object lib/librte_vhost.a.p/vhost_vhost_crypto.c.o
> ninja: build stopped: subcommand failed.
>
>
[-- Attachment #2: Type: text/html, Size: 6731 bytes --]
next prev parent reply other threads:[~2021-10-27 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 5:31 Nigel Kukard
2021-10-27 10:43 ` Tom Barbette [this message]
2021-10-27 11:16 ` David Marchand
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=fecac024-5278-9bd6-85c3-659240789bc0@uclouvain.be \
--to=tom.barbette@uclouvain.be \
--cc=nkukard@LBSD.net \
--cc=users@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).