Re: [PATCH v4] libxml2: upgrade 2.14.6 -> 2.15.0

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

On Fri Nov 7, 2025 at 9:27 AM CET, Hongxu Jia wrote:
> On 11/7/25 15:26, Mathieu Dubois-Briand wrote:
>> CAUTION: This email comes from a non Wind River email account!
>> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>
>> On Wed Nov 5, 2025 at 3:32 AM CET, Hongxu Jia wrote:
>>> Due to upstream [Remove LZMA support][1], drop option --without-lzma
>>>
>>> Due to upstream [disable python bindings by default][2] and are
>>> planned to be removed in the 2.16 release[3][4]. If we still enable
>>> python bindings by --with-python=yes, due to upstream [doc: Build docs
>>> with Doxygen and xsltproc][5], build python binding requires doxygen
>>> otherwise build will fail, and we do not provide doxygen in oe-core,
>>> so remove python package directly.
>>>
>>> Refresh install-tests.patch and run-ptest to not install python test
>>> cases
>>>
>>> Drop CVE-2025-6021.patch which is obsolete
>>>
>>> [1] https://gitlab.gnome.org/GNOME/libxml2/-/commit/1763281cd65ded4067ddf123eb7358690c214b0b
>>> [2] https://gitlab.gnome.org/GNOME/libxml2/-/commit/fa931566d2f541d3162c7b98c8a12e6b2a6ae542
>>> [3] https://download.gnome.org/sources/libxml2/2.15/libxml2-2.15.0.news
>>> [4] https://gitlab.gnome.org/GNOME/libxml2/-/issues/891
>>> [5] https://gitlab.gnome.org/GNOME/libxml2/-/commit/bbe5827c94cc9b0e393ff3e6eef6dec2376317e2
>>>
>>> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
>>> ---
>> Hi Hongxu,
>>
>> Thanks for the new version.
>>
>> It's not clear to me how, but it looks like this update is breaking rust
>> build:
>>
>> ERROR: rust-1.90.0-r0 do_test_compile: Execution of '/srv/pokybuild/yocto-worker/qemuarm64-tc/build/build-st-3876356/tmp/work/cortexa57-poky-linux/rust/1.90.0/temp/run.do_test_compile.3947248' failed with exit code 1
>> ...
>>
>> alues("optimized-c"))' --check-cfg 'cfg(__aarch64_swp8_rel, values("optimized-c"))' --check-cfg 'cfg(__aarch64_swp8_acq_rel, values("optimized-c"))' --check-cfg 'cfg(target_feature, values("vis3"))' --check-cfg 'cfg(feature, values("checked"))' --check-cfg 'cfg(assert_no_panic)' --check-cfg 'cfg(thumb)' --check-cfg 'cfg(thumb_1)' --check-cfg 'cfg(f16_enabled)' --check-cfg 'cfg(f128_enabled)' --check-cfg 'cfg(intrinsics_enabled)' --check-cfg 'cfg(arch_enabled)' --check-cfg 'cfg(optimizations_enabled)' --check-cfg 'cfg(feature, values("unstable-public-internals"))' --check-cfg 'cfg(optimizations_enabled)' --check-cfg 'cfg(x86_no_sse)' --check-cfg 'cfg(kernel_user_helpers)' --check-cfg 'cfg(feature, values("mem-unaligned"))'`
>> | error: rustc interrupted by SIGSEGV, printing backtrace
>> |
>> | /srv/pokybuild/yocto-worker/qemuarm64-tc/build/build-st-3876356/tmp/work/cortexa57-poky-linux/rust/1.90.0/sources/rustc-1.90.0-src/build/x86_64-unknown-linux-gnu/stage1/lib/librustc_driver-d18035d17505fd2b.so(+0xd2ab55) [0x7f3ae2d2ab55]
>> | /srv/pokybuild/yocto-worker/qemuarm64-tc/build/build-st-3876356/tmp/sysroots-uninative/x86_64-linux/lib/libc.so.6(+0x3bba0) [0x7f3ae1e4aba0]
>> | /srv/pokybuild/yocto-worker/qemuarm64-tc/build/build-st-3876356/tmp/work/cortexa57-poky-linux/rust/1.90.0/sources/rustc-1.90.0-src/build/x86_64-unknown-linux-gnu/stage1/lib/librustc_driver-d18035d17505fd2b.so(+0x8527820) [0x7f3aea527820]
>> |
>> | note: we would appreciate a report at https://github.com/rust-lang/rust
>> | help: you can increase rustc's stack size by setting RUST_MIN_STACK=16777216
>> | rustc exited with signal: 11 (SIGSEGV)
>>
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/2610
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/58/builds/672
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/42/builds/2613
>>
>> Can you have a look at these?
>
> Seems no direct relationship with libxml2, but I will still have a look 
> and try to reproduce the rust build failure
>
> //Hongxu

I tried to pick again your patches, and I'm not seeing the same issue
this time. Some tests are still pending, but I'm highly confident they
will succeed.

In addition, the same error also appeared while testing other patches,
completely unrelated with your. So it's more likely that we have some
bad intermittent issue with rust.

Thanks for your time,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com