Re: Meaning of sys_nerr (and porting programs)

2002-01-15 Thread Jeff Bailey
On Mon, Jan 14, 2002 at 08:28:24AM -0600, Gordon Matzigkeit wrote: > I wish I could remember what it was that used sys_nerr like that. It > was back in the old days, so it was probably something like Bash. > > One could always try removing the definition, and see what breaks when > turtle catch

Re: Meaning of sys_nerr (and porting programs)

2002-01-15 Thread Marcus Brinkmann
On Mon, Jan 14, 2002 at 09:59:24AM -0800, Thomas Bushnell, BSG wrote: > Gordon Matzigkeit <[EMAIL PROTECTED]> writes: > > > One could always try removing the definition, and see what breaks when > > turtle catches up. > > I think that's what we should do (at that point it becomes a release > eng

Re: Meaning of sys_nerr (and porting programs)

2002-01-14 Thread Thomas Bushnell, BSG
Gordon Matzigkeit <[EMAIL PROTECTED]> writes: > One could always try removing the definition, and see what breaks when > turtle catches up. I think that's what we should do (at that point it becomes a release engineering issue which Marcus is in the best position to handle). ___

Re: Meaning of sys_nerr (and porting programs)

2002-01-14 Thread Gordon Matzigkeit
[EMAIL PROTECTED] (Thomas Bushnell, BSG) writes: > Roland McGrath <[EMAIL PROTECTED]> writes: > > > 1998-06-01 Gordon Matzigkeit <[EMAIL PROTECTED]> > > > > * sysdeps/mach/hurd/errlist.c (sys_nerr, _sys_nerr): Make weak > > aliases for _hurd_nerr, for programs that don't use sys_errli

Re: Meaning of sys_nerr (and porting programs)

2002-01-13 Thread Thomas Bushnell, BSG
Roland McGrath <[EMAIL PROTECTED]> writes: > 1998-06-01 Gordon Matzigkeit <[EMAIL PROTECTED]> > > * sysdeps/mach/hurd/errlist.c (sys_nerr, _sys_nerr): Make weak > aliases for _hurd_nerr, for programs that don't use sys_errlist, > but need sys_err. First, that's a typo; it sh

Re: Meaning of sys_nerr (and porting programs)

2002-01-13 Thread Roland McGrath
I would have thought sys_nerr should not be defined at all, just as sys_errlist is not. The two go together. In fact, before your report I thought it was not defined. In the libc change logs (libc/ChangeLog.8) I see: 1998-06-01 Gordon Matzigkeit <[EMAIL PROTECTED]> * sysdeps/mach/hu

Re: Meaning of sys_nerr (and porting programs)

2002-01-12 Thread Thomas Bushnell, BSG
Wolfgang Jährling <[EMAIL PROTECTED]> writes: > It allocates an array of sys_nerr elements (the sys_nerr in glibc on > GNU/Hurd is 119) and tries to store an object for each E* constant in > one of those elements, but uses the actual value of the constant as > offset. However, it doesn't crash wh

Meaning of sys_nerr (and porting programs)

2002-01-12 Thread Wolfgang Jährling
Hi! [ This message is about a general issue in GNU/Hurd, which i encountered during i tried to fix Ruby, thus I think it's most relevant for this list. ] I tried to find out more about the problem with the E* constants in Ruby. I found out that Ruby does the following: It allocates an array