DPDK patches and discussions
 help / color / mirror / Atom feed
From: yn h <yncraig123@gmail.com>
To: David Marchand <david.marchand@redhat.com>, dmitry.kozliuk@gmail.com
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] dpdk fail at build.
Date: Tue, 26 Oct 2021 20:43:16 -0400	[thread overview]
Message-ID: <CABpP27HmkC2jC1ASs=+gSwQuv0nQgxVfEX+wTv+5VKcDmO86OQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xzpodhq0Jj8QwXr+BKSvc8GV+nygeZ0bU32DXXms9dRg@mail.gmail.com>

Downgrading to 0.59.0 helped to fix that error, but another error
occurred during ninja build.

[0/1] Installing files.


*ERROR:* Build directory has been generated with Meson version 0.59.0,
which is incompatible with the current version 0.60.0.

FAILED: meson-install

/home/ybuser/.local/bin/meson install --no-rebuild

ninja: build stopped: subcommand failed.

On Mon, Oct 25, 2021 at 5:35 PM David Marchand <david.marchand@redhat.com>
wrote:

> On Mon, Oct 25, 2021 at 11:30 PM yn h <yncraig123@gmail.com> wrote:
> >
> > 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?
>
> It looks like https://bugs.dpdk.org/show_bug.cgi?id=836
> You can try downgrading meson.
>
>
>
> --
> David Marchand
>
>

  reply	other threads:[~2021-10-27 15:09 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
2021-10-25 21:35 ` David Marchand
2021-10-27  0:43   ` yn h [this message]
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='CABpP27HmkC2jC1ASs=+gSwQuv0nQgxVfEX+wTv+5VKcDmO86OQ@mail.gmail.com' \
    --to=yncraig123@gmail.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@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).