From: Pedro Alves <palves@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix tui compilation with Solaris libcurses (PR tui/21482)
Date: Fri, 19 May 2017 13:43:00 -0000 [thread overview]
Message-ID: <14c55a75-c08a-5abc-74df-f59277d7061f@redhat.com> (raw)
In-Reply-To: <yddefvlx9jk.fsf@CeBiTec.Uni-Bielefeld.DE>
On 05/19/2017 02:26 PM, Rainer Orth wrote:
> Hi Eli,
>
>>> I've checked in the cast part now. Here's the NOMACROS part for
>>> gdb_curses.h. Tested as before on sparcv9-sun-solaris2.10 (curses) and
>>> amd64-pc-solaris2.12 (ncurses). Ok too?
>>
>> I think this should be guarded by some OS-specific macro, so as not to
>> affect other platforms, where the original problem doesn't exist. (I
>> see 6 instances of these macros being tested in my ncurses headers,
>> and I'm not on Solaris.) Who knows what new problems this could cause?
>
> that's what I had done initially (via configure.ac for solaris2.* only),
> but Pedro suggested to do it unconditionally since some other targets
> (AIX notably) seem to be having the same problem.
Yes, and it's not host specific, but really curses-implementation
specific. On the same host you may compile against different versions
of curses (BSD curses, ncurses, pdcurses, etc.). I don't see any
benefit to complicate things when we have no evidence that telling
curses to avoid defining its symbols as macros causes problems.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-05-19 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 8:56 Rainer Orth
2017-05-18 13:19 ` Pedro Alves
2017-05-18 13:36 ` Rainer Orth
2017-05-19 12:50 ` Rainer Orth
2017-05-19 12:52 ` Pedro Alves
2017-05-19 13:20 ` Eli Zaretskii
2017-05-19 13:26 ` Rainer Orth
2017-05-19 13:43 ` Pedro Alves [this message]
2017-05-19 13:39 ` Pedro Alves
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=14c55a75-c08a-5abc-74df-f59277d7061f@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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