<div dir="ltr"><div>I was thinking about using CMake's ExternalProject to optionally fetch and build zlib and libxml2 from source, that might be more palatable than including libxml2 in LLVM repository?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 24, 2021 at 10:33 AM Chris Tetreault via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="gmail-m_-7570716906551805529WordSection1">
<p class="MsoNormal">Can we just ship the source for libxml2 in the repository and build it from source if it is not found? A quick google tells me that it’s MIT licensed so perhaps it wouldn’t be too controversial.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> cfe-dev <<a href="mailto:cfe-dev-bounces@lists.llvm.org" target="_blank">cfe-dev-bounces@lists.llvm.org</a>> <b>On Behalf Of
</b>Adrian McCarthy via cfe-dev<br>
<b>Sent:</b> Tuesday, August 24, 2021 10:22 AM<br>
<b>To:</b> Ben Boeckel <<a href="mailto:ben.boeckel@kitware.com" target="_blank">ben.boeckel@kitware.com</a>><br>
<b>Cc:</b> clang developer list <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>><br>
<b>Subject:</b> Re: [cfe-dev] Cannot CMake self-hosted clang on Windows for lack of libxml2<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p align="center" style="text-align:center"><strong><span style="font-size:10.5pt;font-family:Arial,sans-serif;color:black;background:yellow">WARNING:</span></strong><span style="font-size:10.5pt;font-family:Arial,sans-serif;color:black;background:yellow">
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.</span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">> Could an issue please be filed about this? CMake tries hard to not break<br>
backwards compat, though we're not perfect (and we can't fix what we're<br>
not aware of). <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I appreciate that, but I don't think this is a CMake bug.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">In this instance, llvm-mt is supposed to be a cross-platform drop-in alternative for mt.exe. In theory, it shouldn't matter which one CMake selects. And, in fact, the point of a self-hosted build is to use the LLVM tool chain. The fact
that llvm-mt's dependencies aren't met on Windows seems like an LLVM problem, either in the tool itself or in the documentation about how to set up the development environment.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">[Rant about the near-infinite size of LLVM's "supported" configuration space elided, for now.]<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Mon, Aug 23, 2021 at 5:12 PM Ben Boeckel <<a href="mailto:ben.boeckel@kitware.com" target="_blank">ben.boeckel@kitware.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">On Mon, Aug 23, 2021 at 15:17:21 -0700, Adrian McCarthy via cfe-dev wrote:<br>
> Yikes! Thanks for the heads up.<br>
> <br>
> This is the third time I've bisected to find build configuration problems<br>
> that affect only certain Windows configurations only to learn that it was<br>
> (primarily) a change in our tools that broke things (retroactively). Since<br>
> the bot configurations aren't updated very often, it's easy for these<br>
> problems to go unnoticed for a very long time.<br>
<br>
*Puts on CMake developer hat*<br>
<br>
Could an issue please be filed about this? CMake tries hard to not break<br>
backwards compat, though we're not perfect (and we can't fix what we're<br>
not aware of).<br>
<br>
> It's one thing not to have hermetic builds, but it's quite another to allow<br>
> every developer to choose from a wide range of versions for each of the<br>
> myriad tools necessary to build the product. The builds are so sensitive<br>
> to so many details of the environment, it's rather amazing to me how often<br>
> we manage to succeed.<br>
<br>
Yes, and CMake tries not to be the bump in the road there, but we can<br>
fix this in 3.20.6 and 3.21.2 (maybe 3.21.3, depends on how intricate<br>
the fix is).<br>
<br>
Thanks,<br>
<br>
--Ben<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div></div>