Well, I actually ended up writing a compromise of compromises: <div><span style="background-color:rgb(255,255,255);font-family:'Courier New';font-size:12pt"><br></span></div><div><span style="background-color:rgb(255,255,255);font-family:'Courier New';font-size:12pt">The </span><span style="background-color:rgb(255,255,255);font-family:'Courier New';font-size:12pt">recommended course of action is that you do this:</span></div>
<div><div style="font-family:'Courier New';font-size:12pt;background-color:rgb(255,255,255)"><pre>#. Disable your anti-virus solution.
#. Pull the LLVM test suite from the `LLVM website <<a href="http://www.llvm.org">http://www.llvm.org</a>>`_.
#. Add the file ``%LLVMDIR%\\projects\\test-suite\\MultiSource\\Applications\\ClamAV\\inputs\\rtf-test\\rtf1.rtf``
to your anti-virus ignore list. Alternatively, you can, at your own
responsibility, add the entire ``%LLVMDIR%`` directory tree to your
anti-virus solution's ignore list. This will likely speed up your
builds as the anti-virus solution does not need to inspect each and every
file over and over again while building.
</pre></div><div>So, we're covered in all cases. I think the antivirus was the reason that an LLVM build just took about an hour on my Core i7. Normally it only takes like twenty or thirty minutes IF I recall correctly.</div>
<br><div class="gmail_quote">2012/6/16 Joshua Cranmer <span dir="ltr"><<a href="mailto:pidgeot18@gmail.com" target="_blank">pidgeot18@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div><div class="h5">
<div>On 6/15/2012 8:12 PM, Mikael Lyngvig
wrote:<br>
</div>
<blockquote type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Not having
an AV or swithching it off at times is not a sign of<br>
stupidity. The best antivirus is a mindful, knowledgeable
user. And the<br>
antivirus doesn't really protect you in case of risky
behavior.<br>
</blockquote>
<div><br>
</div>
<div>I couldn't have said it better myself. I've had three
viruses in 29 years and only one of them was my own fault.
I've spent hours trying to explain people that trusting an
antivirus solution is unfortunate at best.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Yes, if the antivirus accepts an exception for
a yet nonexistent file. I</div>
bet most of them won't do that without fiddling with
configuration<br>
files.<br>
</blockquote>
<div><br>
</div>
<div>Ok. You get it your way :-) Disable antivirus, checkout,
and then add the offending file to the exclusion list.</div>
</div>
</blockquote>
<br></div></div>
A better rule of thumb I would say is to exclude the entire source
and build directories from antivirus. On-access file scan hurts
build times a fair amount, and I really doubt that any of your
source code is going to have viruses in them :-P<span class="HOEnZb"><font color="#888888"><br>
<pre cols="72">--
Joshua Cranmer
News submodule owner
DXR coauthor</pre>
</font></span></div>
<br>_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
<br></blockquote></div><br></div>