From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: "Anthony Berent" <anthony.berent@arm.com>
Subject: Re: Latest gdb version from CVS will not build!
Date: Mon, 23 Feb 2009 18:37:00 -0000 [thread overview]
Message-ID: <200902231836.55576.pedro@codesourcery.com> (raw)
In-Reply-To: <000301c995e0$976cc270$c6464750$@berent@arm.com>
>Re: Latest gdb version from CVS will not build!
Calm down, it's not the end of the world.
On Monday 23 February 2009 18:00:19, Anthony Berent wrote:
> I am getting errors when I try to build the latest version of gdb from the
> CVS repository for an ARM target. The error I get is in compiling
> remote-sim.c:
>
> gcc -g -O2 -I. -I.././gdb -I.././gdb/config
> -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H
> -I.././gdb/../include/opcode -I.././gdb/../readline/.. -I../bfd
> -I.././gdb/../bfd -I.././gdb/../include -I../libdecnumber
> -I.././gdb/../libdecnumber -I.././gdb/gnulib -Ignulib -DMI_OUT=1 -DTUI=1
> -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral
> -Wno-unused -Wno-switch -Wno-char-subscripts -Werror -c -o remote-sim.o -MT
> remote-sim.o -MMD -MP -MF .deps/remote-sim.Tpo remote-sim.c
> remote-sim.c: In function `init_gdbsim_ops':
> remote-sim.c:900: warning: assignment from incompatible pointer type
> make[2]: *** [remote-sim.o] Error 1
> make[2]: Leaving directory `/home/aberent/gdb-cvs/src-build/gdb'
> make[1]: *** [all-gdb] Error 2
> make[1]: Leaving directory `/home/aberent/gdb-cvs/src-build'
> make: *** [all] Error 2
>
> This appears to be because the signature of the to_resume member of
> target_ops has recently been changed (to include a struct target_ops *
> argument) but no equivalent change has been made to gdbsim_resume in
> remote-sim.c.
Thanks for the report. This is now fixed in CVS.
--
Pedro Alves
prev parent reply other threads:[~2009-02-23 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 18:00 Anthony Berent
2009-02-23 18:37 ` Pedro Alves [this message]
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=200902231836.55576.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=anthony.berent@arm.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