Explicitly disable LIBXML2

It isn't needed and can cause linker problems.

Backport: release

Warnings:

• the merge request is marked as a work-in-progress.

The warnings do not need to be fixed, but it is recommended to do so.

Do: test -i pvbinsdash

This merge request has been queued for testing. Test results may be viewed on:

• CDash (master)
• Buildbot (master) (only visible from inside Kitware)

Branch-at-master: b9c586c6

added 1 commit

• c7b9b5e1 - llvm: explicitly disable LIBXML2

Compare with previous version

Warnings:

• the merge request is marked as a work-in-progress.

The warnings do not need to be fixed, but it is recommended to do so.

added 1 commit

• 07629d4b - llvm: explicitly disable LIBXML2

Compare with previous version

Warnings:

• the merge request is marked as a work-in-progress.

The warnings do not need to be fixed, but it is recommended to do so.

changed the description

Warnings:

• the merge request is marked as a work-in-progress.

The warnings do not need to be fixed, but it is recommended to do so.

Warnings:

• the merge request is marked as a work-in-progress.

The warnings do not need to be fixed, but it is recommended to do so.

Please review, @utkarsh.ayachit @ben.boeckel I'm hoping this resolves a linker problem Alan is seeing, and a related one we saw on the dashboards (addressed in !530 (merged)). Most recent commits just modified the commit message and rebased on release, so I won't run the dashboards again.

sounds reasonable to me, if it's not needed for llvm + mesa.

+1

unmarked as a Work In Progress

Thanks for the review. pvbinsdash is building, so I do not believe it is needed. Plus, it is used only for generating Windows manifest XML files, which shouldn't be needed in this application.

Do: merge

mentioned in commit 4f401ab7

mentioned in commit da66ae97

merged