Re: glibc hppa build failure - ulimit

2005-05-15 Thread Matthew Wilcox
On Sat, May 14, 2005 at 03:15:36PM -0400, Carlos O'Donell wrote: On Fri, May 13, 2005 at 09:26:10PM +0100, Matthew Wilcox wrote: 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.

Re: glibc hppa build failure - ulimit

2005-05-15 Thread Carlos O'Donell
On Sun, May 15, 2005 at 02:52:58PM +0100, Matthew Wilcox wrote: On Sat, May 14, 2005 at 03:15:36PM -0400, Carlos O'Donell wrote: On Fri, May 13, 2005 at 09:26:10PM +0100, Matthew Wilcox wrote: If you want to change glibc at this point, discuss with Carlos; I can't take care of it. Just

Re: glibc hppa build failure - ulimit

2005-05-14 Thread Carlos O'Donell
On Fri, May 13, 2005 at 09:26:10PM +0100, Matthew Wilcox wrote: 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. Carlos? This seems like your fault, how do *you* want to fix it?

glibc hppa build failure - ulimit

2005-05-13 Thread Daniel Jacobowitz
Hi debian-hppa (and -admin), I tried building glibc manually on paer. It didn't work any better. It turns out that ex1 hanging was not the first problem in the build; make crashes building math/others. That's transient, though, and rerunning make got me a build. After much poking at it I am

Re: glibc hppa build failure - ulimit

2005-05-13 Thread Matthew Wilcox
On Fri, May 13, 2005 at 12:17:18PM -0400, Daniel Jacobowitz wrote: 27319 mmap(NULL, 1073741824, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0 unfinished ... 27319 ... mmap resumed ) = -1 ENOMEM (Cannot allocate memory) Right now I don't think we could even

Re: glibc hppa build failure - ulimit

2005-05-13 Thread Daniel Jacobowitz
On Fri, May 13, 2005 at 05:38:33PM +0100, Matthew Wilcox wrote: On Fri, May 13, 2005 at 12:17:18PM -0400, Daniel Jacobowitz wrote: 27319 mmap(NULL, 1073741824, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0 unfinished ... 27319 ... mmap resumed ) = -1 ENOMEM

Re: glibc hppa build failure - ulimit

2005-05-13 Thread Daniel Jacobowitz
On Fri, May 13, 2005 at 12:17:18PM -0400, Daniel Jacobowitz wrote: Hi debian-hppa (and -admin), I tried building glibc manually on paer. It didn't work any better. It turns out that ex1 hanging was not the first problem in the build; make crashes building math/others. That's transient,

Re: glibc hppa build failure - ulimit

2005-05-13 Thread Matthew Wilcox
On Fri, May 13, 2005 at 01:21:48PM -0400, Daniel Jacobowitz wrote: On Fri, May 13, 2005 at 05:38:33PM +0100, Matthew Wilcox wrote: On Fri, May 13, 2005 at 12:17:18PM -0400, Daniel Jacobowitz wrote: 27319 mmap(NULL, 1073741824, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANONYMOUS,

Re: glibc hppa build failure - ulimit

2005-05-13 Thread Daniel Jacobowitz
On Fri, May 13, 2005 at 06:45:35PM +0100, Matthew Wilcox wrote: On Fri, May 13, 2005 at 01:21:48PM -0400, Daniel Jacobowitz wrote: On Fri, May 13, 2005 at 05:38:33PM +0100, Matthew Wilcox wrote: On Fri, May 13, 2005 at 12:17:18PM -0400, Daniel Jacobowitz wrote: 27319 mmap(NULL,

Re: glibc hppa build failure - ulimit

2005-05-13 Thread Matthew Wilcox
On Fri, May 13, 2005 at 02:10:49PM -0400, Daniel Jacobowitz wrote: On Fri, May 13, 2005 at 06:45:35PM +0100, Matthew Wilcox wrote: On Fri, May 13, 2005 at 01:21:48PM -0400, Daniel Jacobowitz wrote: On Fri, May 13, 2005 at 05:38:33PM +0100, Matthew Wilcox wrote: On Fri, May 13, 2005 at

Re: glibc hppa build failure - ulimit

2005-05-13 Thread Daniel Jacobowitz
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

Re: glibc hppa build failure - ulimit

2005-05-13 Thread Matthew Wilcox
On Fri, May 13, 2005 at 03:55:39PM -0400, Daniel Jacobowitz wrote: 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