Re: libc0.3 with gcc-3.0 success

2002-04-08 Thread Jeroen Dekkers
On Mon, Apr 08, 2002 at 08:26:20AM -0700, Jeff Bailey wrote: > On Mon, Apr 08, 2002 at 04:36:32PM +0200, Jeroen Dekkers wrote: > > I don't think that's a showstopper, some of the tests fail with > > stdio too. The iconv and gconv modules aren't that essential, we can > > fix it later IMHO. I don't

Re: libc0.3 with gcc-3.0 success

2002-04-08 Thread Jeroen Dekkers
On Mon, Apr 08, 2002 at 08:31:55AM -0700, Jeff Bailey wrote: > On Mon, Apr 08, 2002 at 05:30:26PM +0200, Jeroen Dekkers wrote: > > > > The testsuite won't even run, which suggests larger problems. I'm > > > not worried about individual tests failing. > > > > I suspect there's not alot to get ri

Re: libc0.3 with gcc-3.0 success

2002-04-08 Thread Jeff Bailey
On Mon, Apr 08, 2002 at 05:30:26PM +0200, Jeroen Dekkers wrote: > > The testsuite won't even run, which suggests larger problems. I'm > > not worried about individual tests failing. > > I suspect there's not alot to get right, and no reason we can't do > > it this week. > Strange, it worked fo

Re: libc0.3 with gcc-3.0 success

2002-04-08 Thread Jeff Bailey
On Mon, Apr 08, 2002 at 04:36:32PM +0200, Jeroen Dekkers wrote: > > The only thing I'm not certain about yet is why make check is > > failing. I've set that as one of my tasks this week. > I don't think that's a showstopper, some of the tests fail with > stdio too. The iconv and gconv modules a

Re: libc0.3 with gcc-3.0 success

2002-04-08 Thread Jeroen Dekkers
On Sun, Apr 07, 2002 at 07:34:51PM -0700, Jeff Bailey wrote: > The only thing I'm not certain about yet is why make check is failing. > I've set that as one of my tasks this week. I don't think that's a showstopper, some of the tests fail with stdio too. The iconv and gconv modules aren't that es

Re: libc0.3 with gcc-3.0 success

2002-04-08 Thread Marcus Brinkmann
On Mon, Apr 08, 2002 at 03:01:26AM -0400, Roland McGrath wrote: > > Do you have any preferance as to when that occurs? > > Not really (you're the people doing the builds that are affected). But I > would like to see some more testing. I thought there were still some > spurious errors that were

Re: libc0.3 with gcc-3.0 success

2002-04-08 Thread Roland McGrath
> Do you have any preferance as to when that occurs? Not really (you're the people doing the builds that are affected). But I would like to see some more testing. I thought there were still some spurious errors that were unexplained, though maybe I am just unclear on which fixes affected which

Re: libc0.3 with gcc-3.0 success

2002-04-07 Thread James Morrison
--- Jeff Bailey <[EMAIL PROTECTED]> wrote: > On Sun, Apr 07, 2002 at 10:12:29PM -0400, Roland McGrath wrote: > > > > Would you consider setting the default stdio for us to libio? > > > It's my intention to do that when and only when we are quite sure we > > are ready to nix the pre-libio packag

Re: libc0.3 with gcc-3.0 success

2002-04-07 Thread Jeff Bailey
On Sun, Apr 07, 2002 at 10:12:29PM -0400, Roland McGrath wrote: > > Would you consider setting the default stdio for us to libio? > It's my intention to do that when and only when we are quite sure we > are ready to nix the pre-libio package archive. Do you have any preferance as to when that o

Re: libc0.3 with gcc-3.0 success

2002-04-07 Thread Roland McGrath
> Would you consider setting the default stdio for us to libio? It's my intention to do that when and only when we are quite sure we are ready to nix the pre-libio package archive. > 1) Try builds with Marcus' ioperms patches. This requires oskit-mach > headers (which I have) but I would pref