Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [6.1] TUI in doco? (compiler errors)
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0403162343030.19039@lazy> (raw)
In-Reply-To: <4057859D.1020900@gnu.org>


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...

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:

:
:
:
:

tui/tui-command.c:91: error: `KEY_NPAGE' undeclared (first use in this
function)
tui/tui-command.c:108: error: `KEY_DOWN' undeclared (first use in this
function)
tui/tui-command.c:109: error: `KEY_SF' undeclared (first use in this
function)
tui/tui-command.c:112: error: `KEY_UP' undeclared (first use in this
function)
tui/tui-command.c:113: error: `KEY_SR' undeclared (first use in this
function)
tui/tui-command.c:116: error: `KEY_RIGHT' undeclared (first use in this
function)
tui/tui-command.c:119: error: `KEY_LEFT' undeclared (first use in this
function)
make[1]: *** [tui-command.o] Error 1
make[1]: Leaving directory `/root/gdb6.1/mar16/gdb'
make: *** [all-gdb] Error 2

I am looking at which definitions are missing, or re-defined.

Thanks
Manoj Iyer

On Tue, 16 Mar 2004, Andrew Cagney wrote:

> Eli,
>
> Any ideas on how to introduce "gdbtui" into the doco?  Once that's
> resolved, I think 6.1 is shippable.
>
> Andrew
>
>


WARNING: multiple messages have this Message-ID
From: Manoj Iyer <manjo@austin.ibm.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [6.1] TUI in doco? (compiler errors)
Date: Tue, 16 Mar 2004 23:21:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0403162343030.19039@lazy> (raw)
Message-ID: <20040316232100.JVyxgP5Q4fKMhQ_4kq16GtsdDMM5fmxoqcf43XfubUI@z> (raw)
In-Reply-To: <4057859D.1020900@gnu.org>


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...

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:

:
:
:
:

tui/tui-command.c:91: error: `KEY_NPAGE' undeclared (first use in this
function)
tui/tui-command.c:108: error: `KEY_DOWN' undeclared (first use in this
function)
tui/tui-command.c:109: error: `KEY_SF' undeclared (first use in this
function)
tui/tui-command.c:112: error: `KEY_UP' undeclared (first use in this
function)
tui/tui-command.c:113: error: `KEY_SR' undeclared (first use in this
function)
tui/tui-command.c:116: error: `KEY_RIGHT' undeclared (first use in this
function)
tui/tui-command.c:119: error: `KEY_LEFT' undeclared (first use in this
function)
make[1]: *** [tui-command.o] Error 1
make[1]: Leaving directory `/root/gdb6.1/mar16/gdb'
make: *** [all-gdb] Error 2

I am looking at which definitions are missing, or re-defined.

Thanks
Manoj Iyer

On Tue, 16 Mar 2004, Andrew Cagney wrote:

> Eli,
>
> Any ideas on how to introduce "gdbtui" into the doco?  Once that's
> resolved, I think 6.1 is shippable.
>
> Andrew
>
>


  parent reply	other threads:[~2004-03-16 23:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 22:54 [6.1] TUI in doco? Andrew Cagney
2004-03-17  5:59 ` Eli Zaretskii
2004-03-19  0:09   ` Eli Zaretskii
2004-03-22 21:30   ` Andrew Cagney
2004-03-23 19:51     ` Eli Zaretskii
2004-03-25 16:26       ` Andrew Cagney
2004-03-25 20:30         ` Eli Zaretskii
2004-03-25 20:40           ` Andrew Cagney
2004-03-26  9:44             ` Eli Zaretskii
2004-03-26 16:23               ` Andrew Cagney
2004-03-19  0:09 ` Manoj Iyer [this message]
2004-03-16 23:21   ` [6.1] TUI in doco? (compiler errors) Manoj Iyer
2004-03-25 22:40   ` Andrew Cagney
2004-03-19  0:09 ` [6.1] TUI in doco? Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.58.0403162343030.19039@lazy \
    --to=manjo@austin.ibm.com \
    --cc=cagney@gnu.org \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox