Hello,
Tim Rice wrote:
> > Can you please try two more snippets?
> >
> > ====================== snippet3.c ========================
> > typedef _Bool ac__type_new_;
> > int
> > main ()
> > {
> > if ((ac__type_new_ *) 0)
> > return 0;
> > if (sizeof (ac__type_new_))
> > return 0;
> > return 0;
> > }
> > ===========================================================
> sh-2.05$ gcc -c snippet3.c
> snippet3.c:1: parse error before `ac__type_new_'
> snippet3.c:1: warning: data definition has no type or storage class
> snippet3.c: In function `main':
> snippet3.c:5: parse error before `)'
This is as expected, thanks.
> > and (remove those #includes that refer to nonexistent files):
> >
> > ====================== snippet4.c ========================
> > #include <stdio.h>
> > #include <sys/types.h>
> > #include <sys/stat.h>
> > #include <stdlib.h>
> > #include <stddef.h>
> > #include <string.h>
> > #include <strings.h>
> > #include <inttypes.h>
> > #include <stdint.h>
> > #include <unistd.h>
> > typedef _Bool ac__type_new_;
> > int
> > main ()
> > {
> > if ((ac__type_new_ *) 0)
> > return 0;
> > if (sizeof (ac__type_new_))
> > return 0;
> > return 0;
> > }
> > ===========================================================
> >
> > $ gcc -c snippet4.c
> > yields what?
> sh-2.05$ gcc -c snippet4.c
> snippet4.c:11: parse error before `ac__type_new_'
> snippet4.c:11: warning: data definition has no type or storage class
> snippet4.c: In function `main':
> snippet4.c:15: parse error before `)'
Well, then in a normal situation the AC_HEADER_STDBOOL macro should not
have set HAVE__BOOL to 1.
I guess you have either the CONFIG_SITE variable set, or a config.site file
somewhere, or passed a --config-cache option to configure, or you configured
for one platform in the same directory as earlier for another platform,
without "make distclean" in between, or something like that?
If you want m4 and gnulib ported to this platform, please start afresh,
without CONFIG_SITE variable, without config.site file, with a freshly
unpacked m4 release tarball and/or with a directory created by
"gnulib-tool --create-testdir --with-tests --dir=.....", and report
all commands that you execute in detail, including configure options, "make"
options, gcc options, etc.
Bruno
