Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kai Tietz <ktietz70@googlemail.com>
To: gdb-patches@sourceware.org
Subject: [patch]: Fix build for GO32 and WIN32 targets
Date: Thu, 21 Jan 2010 14:12:00 -0000	[thread overview]
Message-ID: <90baa01f1001210612v145db5f9m3b4607f602c2ae26@mail.gmail.com> (raw)

Hello,

the function check_syscall in file inflow.c is static, but isn't used
for GO32 and _WIN32 targets. So this leads to "defined but not used"
warning and breaks build. Patch fix this

2010-01-21  Kai Tietz  <kai.tietz@onevision.com>

	* inflow.c (check_syscall): Guard by #if clause for GO32 and WIN32 targets.

Tested for i686-pc-cygwin, x86_64-w64-mingw32, and i686-pc-mingw32. Ok
for apply?

Regards,
Kai

Index: inflow.c
===================================================================
RCS file: /cvs/src/src/gdb/inflow.c,v
retrieving revision 1.56
diff -u -r1.56 inflow.c
--- inflow.c    19 Jan 2010 09:39:12 -0000      1.56
+++ inflow.c    21 Jan 2010 14:11:55 -0000
@@ -633,7 +633,7 @@
   inferior_thisrun_terminal = ttyname;
 }

-
+#if !defined(__GO32__) && !defined(_WIN32)
 /* If RESULT, assumed to be the return value from a system call, is
    negative, print the error message indicated by errno and exit.
    MSG should identify the operation that failed.  */
@@ -646,6 +646,7 @@
       _exit (1);
     }
 }
+#endif

 void
 new_tty (void)



-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination


             reply	other threads:[~2010-01-21 14:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 14:12 Kai Tietz [this message]
2010-01-21 14:15 ` Pedro Alves
2010-01-21 14:26   ` Kai Tietz
2010-01-21 18:00 ` Eli Zaretskii
2010-01-21 21:24   ` Pedro Alves
2010-01-21 22:05     ` Eli Zaretskii
2010-01-21 22:18       ` Pedro Alves
2010-01-22  7:36         ` Eli Zaretskii
2010-01-22 14:08           ` Pedro Alves
2010-01-22 17:09             ` Eli Zaretskii

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=90baa01f1001210612v145db5f9m3b4607f602c2ae26@mail.gmail.com \
    --to=ktietz70@googlemail.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