Bug#91311: semid_ds conflicts with SUSv2
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.
> OK, I see the point is "pedantic" conformance analysis of glibc
> definition, not standard conformance.
Well, it's both really. The standard says X and glibc does Y so clearly
there's a standards conformance thing here. It's just that it's only a
pretty unusual application that's going to notice this particular thing.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
Reply to: