<div dir="ltr">thanks Max, that was exactly what I was interested in.  <div><div>cheers -ben<br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 21, 2017 at 9:12 PM, Max Leske <span dir="ltr"><<a href="mailto:maxleske@gmail.com" target="_blank">maxleske@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><div style="word-wrap:break-word">Hi Ben,<div><br><div><blockquote type="cite"><div>On 21 May 2017, at 15:02, <a href="mailto:vm-dev-request@lists.squeakfoundation.org" target="_blank">vm-dev-request@lists.<wbr>squeakfoundation.org</a> wrote:</div><br class="m_8687026330254232474Apple-interchange-newline"><div><div class="m_8687026330254232474Singleton"><blockquote type="cite" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br>The builds were performed in two separate chroot jails so they did not<br>influence each other. The system is a Debian Jessie, 64 bits.<br><br></blockquote><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Side question - I'm curious how you go about doing a chroot build.  In</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">another thread you could you post some more info on this?</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">cheers -ben</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"></div></div></blockquote></div><br><div><br></div><div>We don't always use chroot but we currently do to build the VM as the build</div><div>- may download stuff from the internet</div><div>- requires installation of 32 bit compat libs</div><div>and we don't want to junk up the system with any of that. Hence, we have a script that creates the chroot for us and prepares all the build dependencies (script attached below). Then we do $ chroot <chroot name> and start compilation (the attached script will create a couple of helper scripts to do that).</div><div><br></div><div>Does that answer your question?</div><div><br></div><div>Cheers,</div><div>Max</div><div><br></div><div></div></div></div><br><div style="word-wrap:break-word"><div><div></div></div></div><br></blockquote></div><br></div></div></div></div>