This is the mail archive of the
libc-hacker@sourceware.cygnus.com
mailing list for the glibc project.
Re: bits/utmpx.h: __ in front of e_exit and e_termination
- To: Mark Kettenis <kettenis@phys.uva.nl>
- Subject: Re: bits/utmpx.h: __ in front of e_exit and e_termination
- From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
- Date: Sun, 6 Dec 1998 14:15:15 +0100
- Cc: libc-alpha@cygnus.com
- References: <199812061256.NAA00140@delius.kettenis.nl>
Am Sun, 06 Dec 1998 schrieb Mark Kettenis:
>From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
> Date: Sat, 5 Dec 1998 13:40:46 +0100
>
> Hi,
>
> ssh-1.2.26 will no longer compile because of this. Is this really
> correct? If so at least bits/utmp.h should be changed too I think.
>
>It is needed to be name-space clean. AFAIK HP-UX does the same. I
>didn't change bits/utmp.h because there is no standard that specifies
>the contents of utmp.h.
>
>We could provide a
>
>#define e_exit __e_exit
>#define e_termination __e_termination
>
>when the user selects some _XXX_SOURCE feature select macro, but I
>couldn't think of a reasonable set to add it to.
Hmm, I may sound stupid, but what has namespace cleanliness to do with that?
ssh-1.2.26 expects the struct members utmpx.ut_exit.e_exit and
utmpx.ut_exit.e_termination, but it doesn't get them if it includes utmpx.h,
but it would get them if it included utmp.h.
Franz.