Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Alfred M. Szmidt" <ams@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gnu-nat.c, compile it without -Werror
Date: Tue, 09 Sep 2008 15:33:00 -0000	[thread overview]
Message-ID: <E1Kd5BZ-0000xj-Fs@fencepost.gnu.org> (raw)
In-Reply-To: <200809091626.06394.pedro@codesourcery.com> (message from Pedro 	Alves on Tue, 9 Sep 2008 16:26:06 +0100)

   Building gnu-nat.c fails with:

   ../../src/gdb/gnu-nat.c: In function 'inf_set_traced':
   ../../src/gdb/gnu-nat.c:884: error: suggest parentheses around assignment used 
   as truth value
   ../../src/gdb/gnu-nat.c:884: error: suggest parentheses around assignment used 
   as truth value
   ../../src/gdb/gnu-nat.c: In function 'inf_signal':
   (... a few more instances of the same ...)

   Turns out that warning comes from the definition of HURD_MSGPORT_RPC,
   a 20+ lines system macro...

   OK?

Fine by me.  Thanks for fixing it.


  reply	other threads:[~2008-09-09 15:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 15:26 Pedro Alves
2008-09-09 15:33 ` Alfred M. Szmidt [this message]
2008-09-10 17:41 ` Joel Brobecker

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=E1Kd5BZ-0000xj-Fs@fencepost.gnu.org \
    --to=ams@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    /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