From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Michael Eager'" <eager@eagercon.com>,
"'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: Build-failure from [PATCH] Support for Xilinx MicroBlaze
Date: Fri, 16 Oct 2009 07:53:00 -0000 [thread overview]
Message-ID: <001501ca4e35$a9392c10$fbab8430$@u-strasbg.fr> (raw)
In-Reply-To: <4AD77877.2050909@eagercon.com>
Linux vadmin 2.6.28-15-server #52-Ubuntu SMP Wed Sep 9 11:50:50 UTC 2009 i686 GNU/Linux
gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3
configured with --enable-targets=all
I get this new build failure:
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/../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 -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wunused-value -Wno-switch -Wno-char-subscripts -Werror -c -o microblaze-linux-tdep.o -MT microblaze-linux-tdep.o -MMD -MP -MF .deps/microblaze-linux-tdep.Tpo ../../src/gdb/microblaze-linux-tdep.c
../../src/gdb/microblaze-linux-tdep.c: In function 'microblaze_linux_memory_remove_breakpoint':
../../src/gdb/microblaze-linux-tdep.c:50: error: 'gdbarch' undeclared (first use in this function)
../../src/gdb/microblaze-linux-tdep.c:50: error: (Each undeclared identifier is reported only once
../../src/gdb/microblaze-linux-tdep.c:50: error: for each function it appears in.)
../../src/gdb/microblaze-linux-tdep.c: In function 'microblaze_linux_sigtramp_cache':
../../src/gdb/microblaze-linux-tdep.c:77: error: 'SP_REGNUM' undeclared (first use in this function)
cc1: warnings being treated as errors
../../src/gdb/microblaze-linux-tdep.c:78: error: implicit declaration of function 'frame_pc_unwind'
../../src/gdb/microblaze-linux-tdep.c:89: error: 'MICROBLAZE_REGISTER_SIZE' undeclared (first use in this function)
../../src/gdb/microblaze-linux-tdep.c: In function 'microblaze_linux_init_abi':
../../src/gdb/microblaze-linux-tdep.c:126: error: passing argument 2 of 'set_gdbarch_memory_remove_breakpoint' from incompatible pointer type
make[1]: *** [microblaze-linux-tdep.o] Error 1
make[1]: Leaving directory `/usr/local/src/gdbcvs/build-mult/gdb'
make: *** [all-gdb] Error 2
Which seems to be realted to the commit
to support microblaze architechture.
Could someone try to fix this?
Pierre Muller
Pascal language support maintainer for GDB
next prev parent reply other threads:[~2009-10-16 7:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 16:32 Michael Eager
2009-10-15 16:44 ` Tom Tromey
2009-10-15 16:47 ` Joel Brobecker
2009-10-15 18:00 ` Tom Tromey
2009-10-15 18:04 ` Tom Tromey
2009-10-15 18:31 ` Joel Brobecker
2009-10-16 12:53 ` Daniel Jacobowitz
2009-10-16 16:14 ` Michael Eager
2009-10-15 17:12 ` Michael Eager
2009-10-15 17:18 ` Joel Brobecker
2009-10-15 18:06 ` Michael Eager
2009-10-15 16:46 ` Joel Brobecker
2009-10-15 17:14 ` Michael Eager
2009-10-15 19:31 ` Michael Eager
2009-10-16 7:53 ` Pierre Muller [this message]
2009-10-16 15:56 ` Build-failure from " Michael Eager
2009-10-16 16:11 ` Pierre Muller
2009-10-16 16:35 ` Joel Brobecker
2009-10-16 23:21 ` Michael Eager
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='001501ca4e35$a9392c10$fbab8430$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=brobecker@adacore.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@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