DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 874] compilation failure extracting libtmp_rte_bus_vdev.a thin archieve
Date: Mon, 01 Nov 2021 11:48:03 +0000	[thread overview]
Message-ID: <bug-874-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=874

            Bug ID: 874
           Summary: compilation failure extracting libtmp_rte_bus_vdev.a
                    thin archieve
           Product: DPDK
           Version: 21.08
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: mayurcools@gmail.com
  Target Milestone: ---

dpdk compilation (which is part of spdk) fails extracting an archieve file as
it was generated as thin archieve.


Found ninja-1.10.2.git.kitware.jobserver-1 at /usr/local/bin/ninja
ninja: Entering directory `/home/mayur/workspace/spdk/dpdk/build-tmp'
[245/264] Generating drivers/rte_bus_vdev.pmd.c with a custom command
FAILED: drivers/rte_bus_vdev.pmd.c
/usr/bin/python3 ../buildtools/gen-pmdinfo-cfile.py
/home/mayur/workspace/spdk/dpdk/build-tmp/buildtools ar
/home/mayur/workspace/spdk/dpdk/build-tmp/drivers/libtmp_rte_bus_vdev.a
drivers/rte_bus_vdev.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/mayur/workspace/spdk/dpdk/build-tmp/drivers/libtmp_rte_bus_vdev.a']'
returned non-zero exit status 1.
[246/264] Generating drivers/rte_bus_pci.pmd.c with a custom command
FAILED: drivers/rte_bus_pci.pmd.c
/usr/bin/python3 ../buildtools/gen-pmdinfo-cfile.py
/home/mayur/workspace/spdk/dpdk/build-tmp/buildtools ar
/home/mayur/workspace/spdk/dpdk/build-tmp/drivers/libtmp_rte_bus_pci.a
drivers/rte_bus_pci.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/mayur/workspace/spdk/dpdk/build-tmp/drivers/libtmp_rte_bus_pci.a']'
returned non-zero exit status 1.
[248/264] Compiling C object lib/librte_vhost.a.p/vhost_vhost_crypto.c.o
ninja: build stopped: subcommand failed.
make[1]: *** [Makefile:148: all] Error 1
make: *** [/home/mayur/workspace/spdk/mk/spdk.subdirs.mk:44: dpdkbuild] Error 2

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-11-01 11:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 11:48 bugzilla [this message]
2021-11-01 12:19 ` bugzilla

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=bug-874-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).