Re: [6.1] TUI in doco? (compiler errors)

Andrew Cagney
2004-03-25T22:40:03Z

> I dont know how much you care abt this for 6.1 to be shippable...
>
> I get compiler errors compiling TUI, I am compiling GDB as a 64bit binary
> on a ppc64 machine, I saw similar compiler errors in ppc-linux-tdep.c,
> because it contained an enum as follows...

I think this was identified as Novell specific? What final include file
and sequence of includes caused the problem?

> enum {
> ELF_NGREG = 48,
> ELF_NFPREG = 33,
> ELF_NVRREG = 33
> };
>
> ELF_XXX are already defined in a header file, so this breaks the build
> beause the latest GCC sees 48 = 48.
>
> I see similar messages with TUI build.
>
> -I./../readline/.. -I../bfd -I./../bfd -I./../include -I../intl
> -I./../intl -DMI_OUT=1 -DTUI=1 -Wimplicit -Wreturn-type -Wcomment
> -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized
> -Wformat-nonliteral -Wunused-label -Wunused-function ./tui/tui-command.c
> cc1: warning: -Wuninitialized is not supported without -O
> In file included from tui/tui-command.c:28:
> tui/tui-data.h:40: error: parse error before "WINDOW"
> tui/tui-data.h:40: warning: no semicolon at end of struct or union
> tui/tui-data.h:52: error: parse error before '}' token
> tui/tui-data.h:224: error: field `data_window' has incomplete type
> tui/tui-data.h:278: error: field `generic' has incomplete type
> In file included from tui/tui-command.c:29:

You're going to need to provide a lot more detail.

Andrew