Skip to contentSkip to conversation

Build fails on FreeBSD 14.0

DPDK/core Bug 1547 [email protected] 3 participants 4 messages Sep 18, 2024

lore
Share & tools
lore

[email protected]

author
#0 lore raw

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: [email protected]
          Reporter: [email protected]

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.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#2 lore raw
Quoted 8 lines · On Wed, Sep 18, 2024 at 01:51:18AM +0000, [email protected] wrote:

[1]Stephen Hemminger changed [2]bug 1547

What Removed Added
Status UNCONFIRMED RESOLVED
Resolution --- INVALID

   [3]Comment # 1 on [4]bug 1547 from [5]Stephen Hemminger

Missing elftools on the build VM

Thanks seems like something that should be caught earlier at the configure stage. I thought that meson checks for pyelftools - is it the python package or the underlying C library that was missing?

/Bruce

#3 lore raw
Quoted 7 lines · On Wed, 18 Sep 2024 09:31:19 +0100 Bruce Richardson…
Quoted 6 lines · On Wed, Sep 18, 2024 at 01:51:18AM +0000, [email protected] wrote:

[1]Stephen Hemminger changed [2]bug 1547

What Removed Added
Status UNCONFIRMED RESOLVED
Resolution --- INVALID

Quoted 8 lines
Quoted 2 lines
   [3]Comment # 1 on [4]bug 1547 from [5]Stephen Hemminger

Missing elftools on the build VM

Thanks seems like something that should be caught earlier at the configure stage. I thought that meson checks for pyelftools - is it the python package or the underlying C library that was missing?

/Bruce

I had updated the FreeBSD VM, and the version of pyelftools package was missing after that. Looks like the version number changed, not sure if docs should be updated?