From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1547] Build fails on FreeBSD 14.0
Date: Wed, 18 Sep 2024 01:49:53 +0000 [thread overview]
Message-ID: <bug-1547-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3048 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1547
Bug ID: 1547
Summary: Build fails on FreeBSD 14.0
Product: DPDK
Version: 24.11
Hardware: All
OS: FreeBSD
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
Current main branch fails build on FreeBSD 14.0
~/DPDK/main $ ninja -C build
ninja: Entering directory `build'
[501/1852] Generating drivers/rte_common_cpt.pmd.c with a custom command
FAILED: drivers/rte_common_cpt.pmd.c
/usr/local/bin/meson runpython ../buildtools/gen-pmdinfo-cfile.py
/home/shemminger/DPDK/main/build/buildtools llvm-ar
/home/shemminger/DPDK/main/build/drivers/libtmp_rte_common_cpt.a
drivers/rte_common_cpt.pmd.c meson runpython ../buildtools/pmdinfogen.py elf
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mesonmain.py", line
186, in run
return options.run_func(options)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mesonmain.py", line
141, in run_runpython_command
runpy.run_path(options.script_file, run_name='__main__')
File "<frozen runpy>", line 291, in run_path
File "<frozen runpy>", line 98, in _run_module_code
File "<frozen runpy>", line 88, in _run_code
File "../buildtools/pmdinfogen.py", line 275, in <module>
main()
File "../buildtools/pmdinfogen.py", line 264, in main
raise Exception("elftools module not found")
Exception: elftools module not found
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mesonmain.py", line
186, in run
return options.run_func(options)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/mesonbuild/mesonmain.py", line
141, in run_runpython_command
runpy.run_path(options.script_file, run_name='__main__')
File "<frozen runpy>", line 291, in run_path
File "<frozen runpy>", line 98, in _run_module_code
File "<frozen runpy>", line 88, in _run_code
File "../buildtools/gen-pmdinfo-cfile.py", line 21, in <module>
subprocess.run(pmdinfogen + paths + [output], check=True)
File "/usr/local/lib/python3.11/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['meson', 'runpython',
'../buildtools/pmdinfogen.py', 'elf',
'/home/shemminger/DPDK/main/build/drivers/libtmp_rte_common_cpt.a.p/common_cpt_cpt_fpm_tables.c.o',
'/home/shemminger/DPDK/main/build/drivers/libtmp_rte_common_cpt.a.p/common_cpt_cpt_pmd_ops_helper.c.o',
'drivers/rte_common_cpt.pmd.c']' returned non-zero exit status 2.
[503/1852] Compiling C object drivers/...n_iavf.a.p/common_iavf_iavf_adminq.c.o
ninja: build stopped: subcommand failed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5101 bytes --]
next reply other threads:[~2024-09-18 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 1:49 bugzilla [this message]
2024-09-18 1:51 ` [DPDK/core Bug 1547] Build fails on FreeBSD 14.0 bugzilla
2024-09-18 8:31 ` Bruce Richardson
2024-09-18 15:08 ` Stephen Hemminger
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-1547-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.