Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: [RFA] Fix compilation failure on cygwin due to ncurses macro.
Date: Wed, 14 Apr 2010 16:30:00 -0000	[thread overview]
Message-ID: <000001cadbef$a21bad70$e6530850$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20100414155944.GK19194@adacore.com>

What about this:
      /* We need to cast the return value of wstandout to void because
         in patches to release "5.7" of ncurses dated after 2009/05/16,
         the wstandout macro expands to code that generates a unused-value
         warning at compilation.  */

  
At least, this is what I understood from the patched ncurses NEWS:

20090516
       + work around antique BSD game's manipulation of stdscr, etc., versus
         SCREEN's copy of the pointer (Debian #528411).
       + add a cast to wattrset macro to avoid compiler warning when
comparing
         its result against ERR (adapted from patch by Matt Kraii, Debian
         #528374).

But I couldn't get the patch itself...
  
Pierre

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : Wednesday, April 14, 2010 6:00 PM
> À : Pierre Muller
> Cc : 'Pedro Alves'; gdb-patches@sourceware.org
> Objet : Re: [RFA] Fix compilation failure on cygwin due to ncurses
> macro.
> 
> > >   /* We need to cast the return value of wstandout to void because
> > >      older versions of the ncurses implementation (for instance,
> > >      the version used with cygwin 1.5) expand to some code leading
> > >      to an unused-value warning from the compiler.  */
> >
> >   Joel, the file I was referring to was generated from
> > `ncurses-5.7/include/ncurses.h.in'
> > which is the last official release of ncurses according to
> > GNU web site, so 'older versions" seems a bit early to me!
> 
> Oh... Can you make an amendment?
> 
> --
> Joel


  reply	other threads:[~2010-04-14 16:30 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 [this message]
2010-04-14 16:33                 ` Joel Brobecker
2010-04-14 16:39                 ` Pedro Alves
2010-04-15  8:09                   ` Pierre Muller
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='000001cadbef$a21bad70$e6530850$@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