From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: add --with-curses to --configuration output
Date: Wed, 15 Feb 2023 14:54:29 -0500 [thread overview]
Message-ID: <482367e3-fd84-011c-56a2-f181cf86a68a@gmail.com> (raw)
In-Reply-To: <0b0c4556-4d34-671d-8632-eb5d44251cfa@simark.ca>
Hi Simon,
Le 2023-02-15 à 13:58, Simon Marchi a écrit :
>> diff --git a/gdb/configure.ac b/gdb/configure.ac
>> index 7c7bf88b3fb..eac1b8f1aba 100644
>> --- a/gdb/configure.ac
>> +++ b/gdb/configure.ac
>> @@ -563,7 +563,10 @@ if test x"$prefer_curses" = xyes; then
>> # search /usr/local/include, if ncurses is installed in /usr/local. A
>> # default installation of ncurses on alpha*-dec-osf* will lead to such
>> # a situation.
>> - AC_SEARCH_LIBS(waddstr, [ncursesw ncurses cursesX curses])
>> + AC_SEARCH_LIBS(waddstr, [ncursesw ncurses cursesX curses],
>> + [AC_DEFINE([HAVE_LIBCURSES], [1],
>> + [Define to 1 if curses is enabled.])
>> + ])
>
> So we now have:
>
> AC_SEARCH_LIBS(waddstr, [ncursesw ncurses cursesX curses],
> [AC_DEFINE([HAVE_LIBCURSES], [1],
> [Define to 1 if curses is enabled.])
> ])
>
> if test "$ac_cv_search_waddstr" != no; then
> curses_found=yes
> fi
>
> I think the `if test ...` serves the same purpose as the action-if-found
> you used. Perhaps consolidate both actions to use the same mechanism?
> Using the action-if-found parameter seems a bit nicer to me.
Yes, this makes sense. I'll do that for v2.
Philippe.
next prev parent reply other threads:[~2023-02-15 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 18:42 Philippe Blain
2023-02-15 18:58 ` Simon Marchi
2023-02-15 19:54 ` Philippe Blain [this message]
2023-02-19 22:37 ` [PATCH v2] " Philippe Blain
2023-02-20 17:08 ` Simon Marchi
2023-02-21 12:52 ` Philippe Blain
2023-02-21 14:36 ` Simon Marchi
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=482367e3-fd84-011c-56a2-f181cf86a68a@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).