From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] elfutils: upgrade 0.195 -> 0.196
Date: Wed, 19 Aug 2026 07:04:41 +0200 [thread overview]
Message-ID: <DKSNPIA0U8TJ.2BL1NWUZH4PRP@bootlin.com> (raw)
In-Reply-To: <20260818140212.55083-1-jaipaul.cheernam@est.tech>
On Tue Aug 18, 2026 at 4:02 PM CEST, Jaipaul Cheernam wrote:
> Source: NEWS
>
> Version 0.196 "Split Personality"
>
> debuginfod: The $DEBUGINFOD_TIMEOUT environment variable is now enforced
> when establishing a connection to a server.
>
> libdw: New functions dwarf_begin_type, dwarf_begin_elf_type and
> dwarf_get_type plus new enum Dwarf_Type. Used to select between
> plain DWARF, split DWARF (.dwo/.dwp) and GNU LTO when opening a
> file.
>
> Added support for DWARF5 supplementary files (.debug_sup) and
> associated DW_FORM_ref_sup4/8 and DW_FORM_strp_sup forms.
>
> Added support for split DWARF debug data when contained in the
> same file as the skeleton.
>
> libdwelf: New functions dwelf_dwarf_debug_sup and dwelf_dwarf_debug_dwp
> for querying .debug_sup and .debug_dwp section data.
>
> libdwfl: Now correctly handles Linux kernel module sections that are
> not present in sysfs.
>
> libdwfl_stacktrace: New functions dwflst_arch_from_uname,
> dwflst_arch_expected_frame_nregs,
> dwflst_arch_sp_dwarf_reg and dwflst_arch_sp_perf_reg
> providing per-architecture constants. The
> libdwfl_stacktrace interface is experimental and may
> be subject to API/ABI changes.
>
> stackprof: New profiling tool for collecting systemwide stacktrace
> profiles. Replaces the eu-stacktrace tool. Requires
> a C++20 capable compiler.
>
> stacktrace: This experimental tool has been removed and replaced with
> eu-stackprof.
>
> srcfiles: Now handles CU names and files from split DWARF.
>
> strip: Fixed bug where a section's sh_link or sh_info reference could
> be missing from the debug file.
>
> version.h: New macro _ELFUTILS_THREAD_SAFE added to <elfutils/version.h>.
> Defined to 1 when the elfutils libraries are built with thread
> safety support enabled. Otherwise it is left undefined.
> Thread safety support is experimental and is not yet officially
> supported.
>
> Dropped patches:
> 0001-libelf-Add-libeu-objects-to-libelf.a-static-archive.patch
> Backported in b4bd2a2bf6 for 0.192 from upstream commit [1].
> A later upstream commit [2] replaced the $(AR) t approach with a
> libeu.manifest file. Both [1] and [2] landed in upstream 0.193,
> making the backport redundant since 0.193. Verified libelf.a
> contains eu-search.o after build without the patch.
>
> [1] https://sourceware.org/git/?p=elfutils.git;a=commit;h=f5d6e088f84dd05278c4698a21cbf1ff4569978d
> [2] https://sourceware.org/git/?p=elfutils.git;a=commit;h=4eff110a60cb9c7b77884c61f5925fe844c52acb
>
> Refreshed patches:
> 0003-musl-utils.patch
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---
Hi Jaipaul,
Thanks for your patch.
It looks like this is breaking ptests:
Failed ptests:
{'elfutils': 'START: ptest-runner\n'
'2026-08-18T20:10\n'
'make \\\n'
'\tTESTS_ENVIRONMENT="libdir=\'/usr/lib\'; bindir=\'/usr/bin\'; '
"LC_ALL=C; LANG=C; VALGRIND_CMD=''; "
"abs_srcdir='/usr/lib/elfutils/ptest/tests'; "
"abs_builddir='/usr/lib/elfutils/ptest/tests'; "
"abs_top_builddir='/usr/lib/elfutils/ptest/tests/../'; export "
'abs_srcdir; export abs_builddir; export abs_top_builddir; export '
'libdir; export bindir; export LC_ALL; export LANG; export '
'VALGRIND_CMD; unset DEBUGINFOD_URLS; '
"NM='riscv64-poky-linux-gcc-nm'; export NM; CC='gcc'; export "
'CC;" \\\n'
'\tLOG_COMPILER="/usr/lib/elfutils/ptest/tests/test-wrapper.sh '
'installed no \'s,^,eu-,\'" check-TESTS\n'
"make[1]: Entering directory '/usr/lib/elfutils/ptest/tests'\n"
"make[1]: *** No rule to make target '../libdw/libdw.a', needed "
"by 'elf-from-memory'.\n"
"make[1]: Target 'check-TESTS' not remade because of errors.\n"
"make[1]: Leaving directory '/usr/lib/elfutils/ptest/tests'\n"
'make: *** [Makefile:3473: installcheck-local] Error 2\n'
'\n'
'ERROR: Exit status is 2\n'
'DURATION: 1\n'}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2197
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4329
https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/1002
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/983
Also, I've seen a build failure of elfutils itself, on qemuarm64
platform. A rebuild is in progress to see if it happens again:
ERROR: elfutils-native-0.196-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/qemuarm64-ptest/build/build/tmp/work/aarch64-linux/elfutils-native/0.196/temp/run.do_compile.861918' failed with exit code 1
...
| gcc -D_GNU_SOURCE -DHAVE_CONFIG_H -DLOCALEDIR='"/srv/pokybuild/yocto-worker/qemuarm64-ptest/build/build/tmp/work/aarch64-linux/elfutils-native/0.196/recipe-sysroot-native/usr/share/locale"' -I. -I../../sources/elfutils-0.196/backends -I.. -iquote. -iquote../../sources/elfutils-0.196/backends -I../../sources/elfutils-0.196/lib -I/srv/pokybuild/yocto-worker/qemuarm64-ptest/build/build/tmp/work/aarch64-linux/elfutils-native/0.196/build -I../../sources/elfutils-0.196/libebl -I../../sources/elfutils-0.196/libasm -I../../sources/elfutils-0.196/libelf -I../../sources/elfutils-0.196/libdw -isystem/srv/pokybuild/yocto-worker/qemuarm64-ptest/build/build/tmp/work/aarch64-linux/elfutils-native/0.196/recipe-sysroot-native/usr/include -Wall -Wshadow -Wformat=2 -Wold-style-definition -Wstrict-prototypes -Wtrampolines -Wlogical-op -Wduplicated-cond -Wnull-dereference -Wimplicit-fallthrough=5 -Wuse-after-free=3 -Wunused -Wextra -Wstack-usage=262144 -D_FORTIFY_SOURCE=3 -isystem/srv/pokybuild/yocto-worker/qemuarm64-ptest/build/build/tmp/work/aarch64-linux/elfutils-native/0.196/recipe-sysroot-native/usr/include -O2 -pipe -c -o sparc_initreg.o ../../sources/elfutils-0.196/backends/sparc_initreg.c
| In file included from ../../sources/elfutils-0.196/backends/aarch64_initreg.c:36:
| /usr/include/linux/uio.h:17:8: error: redefinition of ‘struct iovec’
| 17 | struct iovec
| | ^~~~~
| In file included from /usr/include/aarch64-linux-gnu/bits/fcntl-linux.h:38,
| from /usr/include/aarch64-linux-gnu/bits/fcntl.h:61,
| from /usr/include/fcntl.h:35,
| from ../../sources/elfutils-0.196/lib/system.h:42,
| from ../../sources/elfutils-0.196/backends/aarch64_initreg.c:33:
| /usr/include/aarch64-linux-gnu/bits/types/struct_iovec.h:26:8: note: originally defined here
| 26 | struct iovec
| | ^~~~~
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4312
rebuild: https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4314
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-08-19 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 14:02 [PATCH] elfutils: upgrade 0.195 -> 0.196 Jaipaul Cheernam
2026-08-19 5:04 ` Mathieu Dubois-Briand [this message]
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=DKSNPIA0U8TJ.2BL1NWUZH4PRP@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.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