Re: Non-compliant access behavior?

[J de Boyne Pollard]

ST> But compliancy is also about the common behavior,
ST> and here gcc assumes some behavior of access().

Wrong again.  The problems with access() and what one should do
instead of using access(), have been hashed out some 15 years since.
These include what one should do in order to be properly portable,
which includes *not* simply assuming that group IDs work in only one
way.  I repeat my recommendation to read Bugtraq.  der Mouse, Jeremy
Epstein, and others have already covered this ground, *years ago*.

ST> Then please tell that to gcc people, not me.  
ST> Then please tell that to gcc people, not me.

*You* are the one *with* the problem.  You are the appropriate person
to talk to the gcc maintainers about *your* problem with gcc.