From: Fedin Pavel <p.fedin@samsung.com>
To: insight@sourceware.org
Subject: Build problems again
Date: Mon, 15 Jul 2013 10:01:00 -0000 [thread overview]
Message-ID: <002401ce8142$40fd2680$c2f77380$%fedin@samsung.com> (raw)
Hello! One more build problem appeared:
--- 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../bfd -I./../bfd -I./../include -I../libdecnumber
-I./../libdecnumber -I./gnulib/import -Ibuild-gnulib/import -DGDBTK
-I/mingw/include -Wall -Wdeclar
ation-after-statement -Wpointer-arith -Wpointer-sign -Wno-unused
-Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts
-Wmissing-prototypes -Wdeclaration-after-stateme
nt -Wempty-body -Wmissing-parameter-type -Wold-style-declaration
-Wold-style-definition -Wno-format -Werror -c -o gdbtk.o -MT gdbtk.o -MMD
-MP -MF .deps/gdbtk.Tpo -I./../libgui/sr
c -I/E/Projects/insight/src/tcl/generic
-I/E/Projects/insight/src/tk/generic -I"/E/Projects/insight/src/tk/xlib"
-DGDBTK_LIBRARY=\"/usr/local/share/insight1.0\" -DSRC_DIR=\"/E
/Projects/insight/src/gdb\" ./gdbtk/generic/gdbtk.c
cc1.exe: warnings being treated as errors
./gdbtk/generic/gdbtk.c: In function 'close_bfds':
./gdbtk/generic/gdbtk.c:168:1: error: old-style function definition
make: *** [gdbtk.o] Error 1
--- cut ---
Fixed by changing function definition to:
--- cut ---
void
close_bfds (void)
--- cut ---
(added explicit 'void' in arguments). The error is reported by gcc 4.5.2.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next reply other threads:[~2013-07-15 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 10:01 Fedin Pavel [this message]
2013-07-23 16:41 ` 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:
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='002401ce8142$40fd2680$c2f77380$%fedin@samsung.com' \
--to=p.fedin@samsung.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).