Bug#91311: semid_ds conflicts with SUSv2
At Thu, 13 Mar 2003 13:21:04 +0000,
Mark Brown wrote:
>
> On Thu, Mar 13, 2003 at 12:32:29AM +0900, GOTO Masanori wrote:
> > Mark Brown wrote:
>
> > > --- tendra-4.1.2.orig/src/lib/machines/linux/80x86/startup/xpg3.h
> > > +++ tendra-4.1.2/src/lib/machines/linux/80x86/startup/xpg3.h
> > > @@ -4,8 +4,9 @@
> > > #define _SVID_SOURCE 1
> > > #define _BSD_SOURCE 1
> > > #define __SVR4_I386_ABI_L1__ 1
> > > -#define __semun_defined 1
> > >
> > > #define __WRONG_XPG3_SEARCH_H
> > > #define __WRONG_XPG3_SEARCH_H_SRCH_OLD
> > > #define __WRONG_XPG3_SEARCH_H_SRCH_PROTO
> > > +#define __WRONG_XPG3_SYS_SEM_H
> > > +#define __WRONG_XPG3_SYS_SEM_H_SEM_PROTO
>
> > > One of the last two defines there. I can check further tonight if you
> > > want.
>
> > Yes, please check. My build does not barf the error in sem.[ch] and
> > sem_prot.[ch].
>
> It's __WRONG_XPG3_SYS_SEM_H_SEM_PROTO that's working around the problem.
So did the prior error occur from this issue? Or I guess it's
something other things which is already fixed in these days...
TenDRA things are still "workaround" state, but at least I think glibc
definition satisfies your requirement, linux definition and the
standards (not strictly, but some degree). Could I close this bug?
Regards,
-- gotom
Reply to: