First time here? Check out the FAQ!
When building Veracity on Windows, mt.exe sometimes fails with error code 31. How come?
asked Jul 15 '11 at 13:01
Ian Olsen ♦♦ 4.2k●12●46●69
Usually, this is caused by a virus scanner. Excluding the build directory from your virus software's resident scanner should resolve the problem.
answered Jul 15 '11 at 13:01
Once you sign in you will be able to subscribe for any updates here
Answers
Answers and Comments
Markdown Basics
learn more about Markdown
Tags:
windows ×32 veracity-development ×19
Asked: Jul 15 '11 at 13:01
Seen: 2,022 times
Last updated: Jul 15 '11 at 13:01
How do I build Veracity from source on Windows?
When will Veracity 2.0 be released?
How do I build Veracity from source on OS X using MacPorts?
After building Veracity from source, I see some failures in the test suite. How do I figure out what failed?
What are the Windows equivalents to ~ and @ in Veracity paths?
Is there a Graphical User Interface for Veracity?
Repo on an USB drive: Multiple configs, same machine, different "whoamis", repo without working copy?
CLI error messages - wrong charset
Dealing with third-party libraries for inclusion in Linux distros
What do I do if tests fail after building veracity from source?
powered by OSQA