On 18-Dec-00 at 17:38, Ti Kan ([EMAIL PROTECTED]) wrote:
> Alexander Mai writes:
> > We demand an ANSI conforming compiler and libc for building LessTif.
> > Our configure has (?!) the standard mechanisms of encouraging compilers
> > to switch to this mode not more.
>
> Well UnixWare's cc compiler is ANSI, it's just that the value of __STDC__
> is 0 by default and only goes to 1 when -Xc is used. This means that by
> default (without -Xc), when combined with their version of X11R5's headers
> (which had stuff changed from '#if defined(__STDC__)' to '#if __STDC__')
> wreaked havoc. Because the latter construct not only requires that
> __STDC__ be defined, it has to be > 0. I am tempted to go edit the header
> files and "unfix" their change, but who knows what else that might break. :(
I hate to pass the buck, but this is really an automake problem. The macro
AM_PROG_CC_STDC is supposed to
"try to add an option to output variable CC to make it so."
It also says
"It considers the compiler to be in ANSI C mode if it defintes __STDC__ to 1
and hadles function prototypes correctly."
It seems to be missing something with this compiler.....
>
> > Lots of warnings WRT ANSI violation "can not be" ...
> > We have now some "ignores const" warnings (caused by the stupid X11 stuff
> > which still remains pre-ANSI and never uses const even if more than
> > appropriate) and some cast and comparison problems.
> > What else is there "wrong"? (ok, that's low priority for now)
>
> I think most of the warnings were from the X11R5 header files. If you're
> interested in the actual warnings I can try and compile it again later
> and pull out a few samples.
>
> -Ti (author of xmcd, xmmix)
> --
> /// Ti Kan Vorsprung durch Technik
> /// AMB Research Laboratories, Sunnyvale, CA. USA
> /// [EMAIL PROTECTED]
> ////// http://www.ibiblio.org/tkan/
> ///
>
>
>
