<div dir="ltr">The reason I ask is because I remember several months ago when I originally made these changes, there was quite a bit of difficulty because some of the Jenkins builders were wanting to run libcxx tests without any llvm source tree on the machine.<div><br></div><div>Does this configuration still exist, or is it gone? If it is gone, I think many libcxx maintainers would be very happy if they can assume the presence of an LLVM source tree somewhere on the disk.</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Nov 3, 2017 at 3:18 PM Volodymyr Sapsai <<a href="mailto:vsapsai@apple.com">vsapsai@apple.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">We have llvm source tree next to libcxx and configure libcxx with -DLLVM_PATH.</div><div style="word-wrap:break-word;line-break:after-white-space"><br><div><br><blockquote type="cite"><div>On Nov 2, 2017, at 16:53, Zachary Turner <<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>> wrote:</div><br class="m_-9132299857432366412Apple-interchange-newline"><div><div dir="ltr">No problem. If you don't mind me asking, what was the configuration change you made? Or do you have a link to the patch which fixed it that I can look at?</div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 2, 2017 at 4:43 PM Volodymyr Sapsai via Phabricator <<a href="mailto:reviews@reviews.llvm.org" target="_blank">reviews@reviews.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">vsapsai abandoned this revision.<br>
vsapsai added a comment.<br>
<br>
Fixed by changing libcxx build configuration, no CMake change required.<br>
<br>
<br>
<a href="https://reviews.llvm.org/D39520" rel="noreferrer" target="_blank">https://reviews.llvm.org/D39520</a><br>
<br>
<br>
<br>
</blockquote></div>
</div></blockquote></div><br></div></blockquote></div>