Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>, <gdb-patches@sourceware.org>
Subject: RE: [RFA] Fix compilation failure on cygwin due to ncurses macro.
Date: Thu, 15 Apr 2010 08:09:00 -0000	[thread overview]
Message-ID: <000601cadc72$e751a330$b5f4e990$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <201004141738.22662.pedro@codesourcery.com>

 I finally found the whole series of patches at
http://ftp.ec-m.fr/pub/FreeBSD/ports/local-distfiles/rafan/ncurses/

  The separate NCURSES_CAST(int, (win)->attrs)
was introduced in 20090829 patch.
  According to NEWS, this is to solve Debian #542031.
 
Thus it should become:
      /* We need to cast the return value of wstandout to void because
         in 2009/08/29 patch to release "5.7" of ncurses library,
         the wstandout macro expands to code that generates a unused-value
         warning at compilation.  */

Is this correct?

Pierre


  reply	other threads:[~2010-04-15  8:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13  8:56 Pierre Muller
2010-04-13 11:38 ` Pedro Alves
2010-04-13 12:13   ` Pierre Muller
2010-04-13 15:07     ` Joel Brobecker
2010-04-13 15:17       ` Pierre Muller
2010-04-13 15:26         ` Joel Brobecker
2010-04-14 11:08           ` Pierre Muller
2010-04-14 16:00             ` Joel Brobecker
2010-04-14 16:30               ` Pierre Muller
2010-04-14 16:33                 ` Joel Brobecker
2010-04-14 16:39                 ` Pedro Alves
2010-04-15  8:09                   ` Pierre Muller [this message]
2010-04-15 15:53                     ` Joel Brobecker
2010-04-15 22:38                       ` [RFC] Use macro for void typecast necessary for ncurses library Pierre Muller
2010-04-16  4:36                         ` Joel Brobecker
     [not found]                       ` <9120.2086922296$1271371097@news.gmane.org>
2010-04-20 15:45                         ` Tom Tromey

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='000601cadc72$e751a330$b5f4e990$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=brobecker@adacore.com \
    --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