On Mon, Nov 25, 2002 at 05:06:22PM -0800, Roland McGrath wrote:
> > init_first.c now fails to compile with the following errors:
> Oops, my bad. I think and are what it needs.
> Can you test that?
That appears to fix it. Thanks!
Tks,
Jeff Bailey
__
> init_first.c now fails to compile with the following errors:
Oops, my bad. I think and are what it needs.
Can you test that?
> ../sysdeps/mach/hurd/i386/init-first.c: In function `posixland_init':
> ../sysdeps/mach/hurd/i386/init-first.c:68: `_dl_starting_up' undeclared (first use
>this fun
On Thu, Nov 21, 2002 at 08:24:21PM -0800, Roland McGrath wrote:
> > math/test-fpucw.out
> >
> > control word is 0x23f but should be 0x33f.
> I imagine this explains the other math results, which otherwise
> should not differ from Linux/x86. I put in a change to init-first.c
> that might fix i
On Thu, 2002-11-21 at 23:24, Roland McGrath wrote:
> > assert/test-assert-perr.out
> >
> > Blank file
>
> It's always empty. Do you mean it exitted with nonzero?
Yes, it exitted with 1.
--
When you get to the heart,
use a knife and fork.
- From instructions on how to eat an artichoke.
s
> assert/test-assert-perr.out
>
> Blank file
It's always empty. Do you mean it exitted with nonzero?
> math/test-fenv.out
>
> Test: after fesetenv (FE_NOMASK_ENV) processes will abort
> when feraiseexcept (FE_INVALID) is called.
> Fail: Process didn't receive signal and exited
FYI, I've just run make check on glibc for the Hurd (2.3.1 with various
Debian patches)
I'm pleased that all of the locales stuff appears to pass (I last ran
make check when we still used stdio)
This post is mostly informational and in case some brave hacker feels
like figuring them out over wint
