On 09/09/13 17:19, William Harrington wrote:
On Aug 28, 2013, at 5:03 PM, Martin Ward wrote:
Did add ulimit -s 32768 before testing though, and disabled those
pesky mudflap test which have failed in the same place for ages.
Martin
Hello Martin,
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.
Perhaps get the ulimit stack value in a variable then set it, then
unset it with th evariable and unset the variable maybe:
STACK=`ulimit -s`
ulimit -s 32768
<do tests here>
ulimit -s ${STACK}
Or is it okay to leave the stack size that huge for the remainder of
the build?
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
Or is there a way to set the stack size without ulimit during the test
phase, such as a variable somewhere?
Not that I Know of.
SIncerely,
William Harrington
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
Cheers
Martin
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
