Tomi Vainio - Sun Finland <[EMAIL PROTECTED]> writes:
> Dan Espen writes:
> >
> > The problem is that 2.5.5 was created with
> > autoconf 2.53 where 2.4.15 used something earlier.
> >
> > The nightly snapshots are generated with 2.13,
> > so they should work fine.
> >
> > Will you contact the autoconf developers?
> >
> If you know what is the problem it might be much better if you contact
> them.
I don't really understand the ins and outs.
This is the code:
#include <stdio.h>
#ifdef F77_DUMMY_MAIN
# ifdef __cplusplus
extern "C"
# endif
int F77_DUMMY_MAIN() { return 1; }
#endif
int
main ()
{
int warn(void) {
int i; static j; int *p; char *c;
switch (*p = p = *c) { case 0: printf("%Q", c, p); }
*c = &i; c = p;
while (1 || (unsigned int)3 >= 0 || ((int)-1) == ((unsigned int)1));
return; }
;
return 0;
}
I think they want it to generate a warning.
It does with gcc.
With forte 6.2 on my Solaris 8 machine, it generates an error:
fork> cc x.c
"x.c", line 11: syntax error before or at: {
Line 11 is:
int warn(void) {
I really don't know what that is.
It looks like a function within a function.
Thats what gcc seems to treat it as:
fork> gcc x.c
x.c: In function `warn':
x.c:13: warning: assignment makes pointer from integer without a cast
x.c:13: warning: assignment makes integer from pointer without a cast
x.c:14: warning: assignment makes integer from pointer without a cast
x.c:14: warning: assignment from incompatible pointer type
Maybe someone else on the list can clarify.
--
Dan Espen E-mail: [EMAIL PROTECTED]
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
