<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 9, 2013, at 11:32 AM, Martin Ward wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><blockquote type="cite">Hello Martin,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thinking about adding this to the book. Although we set it before the test. Should we set ulimit back to the old setting after the test.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Perhaps get the ulimit stack value in a variable then set it, then unset it with th evariable and unset the variable maybe:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">STACK=`ulimit -s`<br></blockquote><blockquote type="cite">ulimit -s 32768<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><do tests here><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">ulimit -s ${STACK}<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Or is it okay to leave the stack size that huge for the remainder of the build?<br></blockquote><blockquote type="cite"><br></blockquote><br>You can logout and login in again , if your following the boot method, Bit of a pain if chrooting though, I've haven't had any problems when I've done it<br><blockquote type="cite"><br></blockquote><blockquote type="cite">Or is there a way to set the stack size without ulimit during the test phase, such as a variable somewhere?<br></blockquote><blockquote type="cite"><br></blockquote><br>Not that I Know of.</div></span></blockquote></div><br><div><br></div><div>Are there any other test suite changes that need to be made in other packages? </div><div><br></div><div>I saw the gcc mailing list entry about stack size issues, most likely changing the stack size will be a note (the default is 8192 as far as I know), and have the user set it optionally. I'm not sure. Could make it a userinput command so it is there when dumping the command as well.</div><div><br></div><div>Sincerely,</div><div><br></div><div>William Harrington</div></body></html>