public inbox for
 help / color / mirror / Atom feed
From: Fedin Pavel <>
Subject: Problem building Insight
Date: Thu, 16 May 2013 07:28:00 -0000	[thread overview]
Message-ID: <000701ce5206$f8a4e2c0$e9eea840$> (raw)


 I have an error building fresh Insight from the CVS:
--- cut ---
gcc -O2 -isystem /mingw/include -D__USE_MINGW_ACCESS   -I. -I. -I./common
-I./config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H
-I./../include/opcode -I./../opcodes/.. -I./../readline/.. -I../b
fd -I./../bfd -I./../include -I../libdecnumber -I./../libdecnumber
-I./gnulib/import -Ibuild-gnulib/import   -DGDBTK -I/mingw/include  -Wall
-Wdeclaration-after-statement -Wpointer-arith -Wpointer-sign -Wno-
unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts
-Wmissing-prototypes -Wdeclaration-after-statement -Wempty-body -Wno-format
-Werror -c -o gdbtk-cmds.o -MT gdbtk-cmds.o -MMD -MP -MF .d
eps/gdbtk-cmds.Tpo -I./../libgui/src
-I/e/Projects/insight/src/tcl/generic -I/e/Projects/insight/src/tk/generic
-DGDBTK_LIBRARY=\"/usr/local/share/insight1.0\" -DSRC_DI
R=\"/e/Projects/insight/src/gdb\" ./gdbtk/generic/gdbtk-cmds.c
cc1.exe: warnings being treated as errors
./gdbtk/generic/gdbtk-cmds.c: In function 'gdb_update_mem':
./gdbtk/generic/gdbtk-cmds.c:2550:9: error: pointer targets in passing
argument 4 of 'target_read' differ in signedness
./target.h:325:16: note: expected 'gdb_byte *' but argument is of type 'char
make[2]: *** [gdbtk-cmds.o] Error 1
make[2]: Leaving directory `/e/Projects/insight/src/gdb'
--- cut ---
 The simplest way to fix this was to add an explicit cast of this argument
to the required type.

 Kind regards.

             reply	other threads:[~2013-05-16  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  7:28 Fedin Pavel [this message]
2013-05-16  7:46 ` Fedin Pavel
2013-05-16 15:50   ` Keith Seitz

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:

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

  git send-email \
    --in-reply-to='000701ce5206$f8a4e2c0$e9eea840$' \ \ \

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