<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>Hi Eliot<br><div id="1"><br>>a and ast are prefixes for assert. There are three VM configurations. Debug and Assert include assert code, with the Assert VMs being optimized with -O1 (asserts are slow to evaluate and a little optimization can really help). Debug VMs are entirely unoptimized (and hence crawl). >The third is production where asserts are eliminated by the preprocessor.</div><div>>Obviously I should be consistent and withe ruse a or ast, not both (and the same for d/bg). <strong>I'm about to revise the whole build directory stricture anyway to make it much more consistent, but I've yet to find the time.</strong></div><div><strong><br></strong></div><div>If you have time to give me that naming convention, I will build that directory structure for you and send it to you as a tarball, complete with the existing files so it saves you some time there.<strong><br></strong></div><div><br></div><div>>>The "t" suffix is for "threaded" and means that these VMs have the threaded heartbeat, with the others using the problematic itimer heartbeat. Alas older linux kernels don't allow the threaded heartbeat, but once we're not interested in supporting older then 2.6.14 (IIRC) then they can be dropped.</div><blockquote style="border-left: 1px solid #0000FF; padding-left: 6px; margin:0 0 0 5px"><div dir="ltr"><div><div> </div></div></div></blockquote><div><br></div><div>Is 'mt' is that the same as 't' ?</div><div><br></div><div><br></div><div><br></div><div><br></div><div>tty</div><div><br></div></div></body></html>