envoyproxy / envoyproxy/envoy

After llvm22, libxml2 needs to be provided by the host instead of the hermetic tool chain

Open
#46,384 8 comments 0 reactions 0 assignees View on GitHub
area/build bug no stalebot
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
428

Description

*Title*: After llvm22, libxml2 needs to be provided by the host instead from the hermetic tool chain

*Description*:
when synced past #46371 , we start seeing link error requesting libxml2. Is this expected? Should the hermetic tool chain carry `libxml2` instead?

*Repro steps*:
On a host without `libxml2` installed, just bazel build any thing with `--config=clang`.

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. First reproduce the failure on a host without libxml2 with `bazel build` and `--config=clang`, then inspect the hermetic tool chain and the changes after LLVM 22. Done means the expected libxml2 dependency behavior is established and the reported build no longer fails under the documented host condition.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.