On Fri, May 13, 2005 at 08:32:53PM +0100, Matthew Wilcox wrote: > Well, how can we fix this for sarge then? Either we need to change glibc > or the kernel, both of which are extremely deeply frozen. I'd rather > fix this by reverting to our previous behaviour of assuming 8MB stacks > for threads than change the kernel's behaviour to limit stacks to 8MB > by default. That would seem to risk breaking much more stuff.
I'm not following. Are you saying that the changed ulimit is the result of a kernel change? That seems very strange, since sarti has a 134 day uptime and did not have this problem building glibc a month ago for -21. If you want to change glibc at this point, discuss with Carlos; I can't take care of it. Just getting -22 built has taken most of my free time for this week. -- Daniel Jacobowitz CodeSourcery, LLC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]