From: Hui Zhu <teawater@gmail.com>
To: insight@sourceware.org
Subject: Get build error
Date: Tue, 30 Nov 2010 13:05:00 -0000 [thread overview]
Message-ID: <AANLkTi==QEWg1Thfm3im5LTyD7GcnyTa9AR3aiH=gF7+@mail.gmail.com> (raw)
gcc -g -O2 -I. -I../../src/gdb -I../../src/gdb/common
-I../../src/gdb/config -DLOCALEDIR="\"/usr/local/share/locale\""
-DHAVE_CONFIG_H -I../../src/gdb/../include/opcode
-I../../src/gdb/../opcodes/.. -I../../src/gdb/../readline/.. -I../bfd
-I../../src/gdb/../bfd -I../../src/gdb/../include -I../libdecnumber
-I../../src/gdb/../libdecnumber -I../../src/gdb/gnulib -Ignulib
-DMI_OUT=1 -DTUI=1 -DGDBTK -Wall -Wdeclaration-after-statement
-Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused
-Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts
-Werror -c -o gdbtk-hooks.o -MT gdbtk-hooks.o -MMD -MP -MF
.deps/gdbtk-hooks.Tpo -I../../src/gdb/../libgui/src
-I/home/teawater/gdb/cvs/src/tcl/generic
-I/home/teawater/gdb/cvs/src/tk/generic
-DGDBTK_LIBRARY=\"/usr/local/share/insight1.0\"
-DSRC_DIR=\"/home/teawater/gdb/cvs/src/gdb\"
../../src/gdb/gdbtk/generic/gdbtk-hooks.c
../../src/gdb/gdbtk/generic/gdbtk-hooks.c: In function 'gdbtk_annotate_signal':
../../src/gdb/gdbtk/generic/gdbtk-hooks.c:811: error: 'struct
thread_info' has no member named 'stop_signal'
../../src/gdb/gdbtk/generic/gdbtk-hooks.c:812: error: 'struct
thread_info' has no member named 'stop_signal'
make[2]: *** [gdbtk-hooks.o] Error 1
make[2]: Leaving directory `/home/teawater/gdb/cvs/ba/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/home/teawater/gdb/cvs/ba'
make: *** [all] Error 2
next reply other threads:[~2010-11-30 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 13:05 Hui Zhu [this message]
2010-12-02 2:15 ` Hui Zhu
2010-12-02 2:33 ` Keith Seitz
2010-12-02 8:25 ` Hui Zhu
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='AANLkTi==QEWg1Thfm3im5LTyD7GcnyTa9AR3aiH=gF7+@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).