From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHSET] [4/4] Fix various issue in TUI
Date: Thu, 22 Jan 2015 17:15:00 -0000 [thread overview]
Message-ID: <54C13014.6050306@redhat.com> (raw)
In-Reply-To: <83lhkuvl1v.fsf@gnu.org>
On 01/22/2015 04:26 PM, Eli Zaretskii wrote:
>> Date: Thu, 22 Jan 2015 12:07:26 +0000
>> From: Pedro Alves <palves@redhat.com>
>> CC: gdb-patches@sourceware.org
>>
>>>>>>> On 12/31/2014 05:56 PM, Eli Zaretskii wrote:
>>>>>>>>> Well, one patch is Windows-specific after all. This patch makes sure
>>>>>>>>> windows-termcap is not compiled when GDB is linked against ncurses,
>>>>>>>
>>>>>>> ...
>>>>>>>
>>>>>>>>> and also makes the file a no-op should it compile in that
>>>>>>>>> configuration.
>>>>>>>
>>>>>>> With the configure.ac change, how can that happen?
>>>>>
>>>>> It shouldn't.
>>
>> I'd have preferred to drop that hunk then. It just seems to
>> be either pointless or hiding some problem with the
>> configure.ac check.
>
> At the very least how about an #error in those conditions? Otherwise,
> any bit-rot (something that happens now and then with the MinGW build)
> will silently do the wrong thing.
Well, I fear that the #ifdefery can bit rot just as well. So having
two places that can bitrot (configure and #ifdef) seems worse than
one.
>>
>> So shouldn't the right check be this:
>>
>> if test x"$curses_found" != xyes; then
>> ac_cv_search_tgetent="none required"
>> CONFIG_OBS="$CONFIG_OBS windows-termcap.o"
>> fi ;;
>>
>> ?
>
> I'm not sure. GDB can be configured --without-tui --with-curses.
> Does your logic work then?
It's the same thing. That sets $prefer_curses:
opt_curses=no
AC_ARG_WITH(curses, AS_HELP_STRING([--with-curses], [use the curses library instead of the termcap library]), opt_curses=$withval)
prefer_curses=no
if test "$opt_curses" = "yes"; then
prefer_curses=yes
fi
But that doesn't mean that curses will be used. We'll again fall here:
curses_found=no
if test x"$prefer_curses" = xyes; then
...
AC_SEARCH_LIBS(waddstr, [ncurses cursesX curses])
if test "$ac_cv_search_waddstr" != no; then
curses_found=yes
fi
fi
And if waddstr is not found, meaning curses is not really
available, even though it'd be preferred, $prefer_curses is
yes, but $curses_found is no.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-01-22 17:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 17:56 Eli Zaretskii
2015-01-05 19:55 ` Pedro Alves
2015-01-05 20:06 ` Eli Zaretskii
2015-01-17 9:55 ` Eli Zaretskii
2015-01-19 14:50 ` Joel Brobecker
2015-01-19 16:26 ` Eli Zaretskii
2015-01-19 16:54 ` Joel Brobecker
2015-01-19 15:43 ` Joel Brobecker
2015-01-19 17:31 ` Eli Zaretskii
2015-01-19 17:54 ` Joel Brobecker
2015-01-22 12:07 ` Pedro Alves
2015-01-22 16:26 ` Eli Zaretskii
2015-01-22 17:15 ` Pedro Alves [this message]
2015-01-22 17:30 ` Eli Zaretskii
2015-01-22 18:36 ` 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=54C13014.6050306@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--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