Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Clint Thomas" <cthomas@Soneticom.com>
To: <gdb@sourceware.org>
Subject: Cross Compile GDB 6.6 PPC405
Date: Wed, 14 Feb 2007 20:24:00 -0000	[thread overview]
Message-ID: <3C02138692C13C4BB675FE7EA2409529297FA2@bluefin.Soneticom.local> (raw)

Hey guys,

I am trying to build a native GDB to run on my powerpc-405 target. To do
this, I run the configure script in gdb-6.6 as such ./configure
--build=i386-linux-gnu --target=powerpc-405-linux-gnu
--host=powerpc-405-linux-gnu Now beforehand, I tried building this, and
the make would always fail with the error "No Termcap Library found".
After finding out that the --builduserland option is broken, I tried
cross-compiling ncurses manually. After doing that, I moved the contents
of the ../ncurses/lib directory into the directory containing libc.a in
my cross-compiler directory. Now when I build GDB, I get this output

 

powerpc-405-linux-gnu-gcc -c -g -O2 -I. -I.././gdb -I.././gdb/config
-LOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H
-I.././gdb/../include/opcode -I.././gdb/../readline/..-I../bfd
-I.././gdb/../bfd -I.././gdb/../include -DMI_OUT=1 -DTUI=1 -Wimplicit
-Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses
-Wpointer-arith -Wformat-nonliteral -Wunused-label -Wunused-function
-Wuninitialized .././gdb/tui/tui-command.c 

In file included from .././gdb/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:228: error: field `data_window' has incomplete type

./tui/tui-data.h:282: error: field `generic' has incomplete type In file
included from .././gdb/tui/tui-command.c:29:

./tui/tui-win.h:42: error: parse error before "tui_border_ulcorner"

./tui/tui-win.h:42: warning: type defaults to `int' in declaration of
`tui_border_ulcorner'

./tui/tui-win.h:42: warning: data definition has no type or storage
class

./tui/tui-win.h:43: error: parse error before "tui_border_urcorner"

./tui/tui-win.h:43: warning: type defaults to `int' in declaration of
`tui_border_urcorner'

./tui/tui-win.h:43: warning: data definition has no type or storage
class

./tui/tui-win.h:44: error: parse error before "tui_border_lrcorner"

./tui/tui-win.h:44: warning: type defaults to `int' in declaration of
`tui_border_lrcorner'

./tui/tui-win.h:44: warning: data definition has no type or storage
class

./tui/tui-win.h:45: error: parse error before "tui_border_llcorner"

./tui/tui-win.h:45: warning: type defaults to `int' in declaration of
`tui_border_llcorner'

./tui/tui-win.h:45: warning: data definition has no type or storage
class

./tui/tui-win.h:46: error: parse error before "tui_border_vline"

./tui/tui-win.h:46: warning: type defaults to `int' in declaration of
`tui_border_vline'

./tui/tui-win.h:46: warning: data definition has no type or storage
class

./tui/tui-win.h:47: error: parse error before "tui_border_hline"

./tui/tui-win.h:47: warning: type defaults to `int' in declaration of
`tui_border_hline'

./tui/tui-win.h:47: warning: data definition has no type or storage
class

.././gdb/tui/tui-command.c: In function `tui_dispatch_ctrl_char':

.././gdb/tui/tui-command.c:80: error: `WINDOW' undeclared (first use in
this function)

.././gdb/tui/tui-command.c:80: error: (Each undeclared identifier is
reported only once

.././gdb/tui/tui-command.c:80: error: for each function it appears in.)

.././gdb/tui/tui-command.c:80: error: `w' undeclared (first use in this
function)

.././gdb/tui/tui-command.c:85: warning: implicit declaration of function
`wgetch'

.././gdb/tui/tui-command.c:86: error: `ERR' undeclared (first use in
this function)

.././gdb/tui/tui-command.c:93: error: `KEY_PPAGE' undeclared (first use
in this function)

.././gdb/tui/tui-command.c:95: error: `KEY_NPAGE' undeclared (first use
in this function)

.././gdb/tui/tui-command.c:113: error: `KEY_DOWN' undeclared (first use
in this function)

.././gdb/tui/tui-command.c:114: error: `KEY_SF' undeclared (first use in
this function)

.././gdb/tui/tui-command.c:117: error: `KEY_UP' undeclared (first use in
this function)

.././gdb/tui/tui-command.c:118: error: `KEY_SR' undeclared (first use in
this function)

.././gdb/tui/tui-command.c:121: error: `KEY_RIGHT' undeclared (first use
in this function)

.././gdb/tui/tui-command.c:124: error: `KEY_LEFT' undeclared (first use
in this function)

make[2]: *** [tui-command.o] Error 1

make[2]: Leaving directory `/home/cthomas/gdb-6.6/gdb'

make[1]: *** [all-gdb] Error 2

make[1]: Leaving directory `/home/cthomas/gdb-6.6'

make: *** [all] Error 2

I've been looking around the mailing lists, it seems like the problem is
related to ncurses, but I am unsure of what I am doing wrong, as I have
not found a good solution to my problem of building GDB to run native on
my target.

Clinton Thomas


             reply	other threads:[~2007-02-14 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 20:24 Clint Thomas [this message]
2007-02-14 20:27 ` Daniel Jacobowitz
2007-02-14 20:48   ` Khem Raj
2007-02-17  8:51     ` Clint Thomas
2007-02-15  7:35 ` Michael Snyder

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=3C02138692C13C4BB675FE7EA2409529297FA2@bluefin.Soneticom.local \
    --to=cthomas@soneticom.com \
    --cc=gdb@sourceware.org \
    /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