From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: yn h <yncraig123@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] dpdk fail at build.
Date: Tue, 26 Oct 2021 00:34:59 +0300 [thread overview]
Message-ID: <20211026003459.3d713746@sovereign> (raw)
In-Reply-To: <CABpP27HVrootbLCO88Wu8gJoJzOP=dq97ffgJyziX0e-j6x6hg@mail.gmail.com>
2021-10-25 17:11 (UTC-0400), yn h:
> I downloaded dpdk version 21.08 from
> http://static.dpdk.org/rel/.
>
> Extracted and ran meson build.
> During ninja build, I ran into
>
> FAILED: drivers/rte_common_cpt.pmd.c
>
> /usr/bin/python3 ../buildtools/gen-pmdinfo-cfile.py
> /home/ybuser/dpdk-21.05/build/buildtools ar
> /home/ybuser/dpdk-21.05/build/drivers/libtmp_rte_common_cpt.a
> drivers/rte_common_cpt.pmd.c /usr/bin/python3 ../buildtools/pmdinfogen.py
> elf
>
> ar: `x' cannot be used on thin archives.
>
> Traceback (most recent call last):
>
> File "../buildtools/gen-pmdinfo-cfile.py", line 17, in <module>
>
> run_ar("x")
>
> File "../buildtools/gen-pmdinfo-cfile.py", line 12, in <lambda>
>
> run_ar = lambda command: subprocess.run(
>
> File "/usr/lib/python3.8/subprocess.py", line 516, in run
>
> raise CalledProcessError(retcode, process.args,
>
> subprocess.CalledProcessError: Command '['ar', 'x',
> '/home/ybuser/dpdk-21.05/build/drivers/libtmp_rte_common_cpt.a']' returned
> non-zero exit status 1.
>
> [508/2498] Compiling C object
> lib/librte_pipeline.a.p/pipeline_rte_table_action.c.o
>
> ninja: build stopped: subcommand failed.
>
>
>
> The issue was bypassed when I edited the run_ar("x") to run_ar("p").
>
> Is this a known issue?
Yes, try using meson < 0.60:
https://bugs.dpdk.org/show_bug.cgi?id=836
next prev parent reply other threads:[~2021-10-25 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 21:11 yn h
2021-10-25 21:34 ` Dmitry Kozlyuk [this message]
2021-10-25 21:35 ` David Marchand
2021-10-27 0:43 ` yn h
2021-10-27 9:44 ` 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=20211026003459.3d713746@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=yncraig123@gmail.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).