From: Simon Marchi <simark@simark.ca>
To: Philippe Blain <levraiphilippeblain@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb: add --with-curses to --configuration output
Date: Tue, 21 Feb 2023 09:36:54 -0500 [thread overview]
Message-ID: <03f11e34-1a30-6712-09a2-8983e68d1a70@simark.ca> (raw)
In-Reply-To: <e8da0087-d588-0373-a6f6-6e795cadf556@gmail.com>
On 2/21/23 07:52, Philippe Blain wrote:
> Hi Simon,
>
> Le 2023-02-20 à 12:08, Simon Marchi a écrit :
>>> diff --git a/gdb/configure.ac b/gdb/configure.ac
>>> index 7c7bf88b3fb..6ad0f9d8815 100644
>>> --- a/gdb/configure.ac
>>> +++ b/gdb/configure.ac
>>> @@ -563,11 +563,11 @@ 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])
>>> -
>>> - if test "$ac_cv_search_waddstr" != no; then
>>> - curses_found=yes
>>> - fi
>>> + AC_SEARCH_LIBS(waddstr, [ncursesw ncurses cursesX curses],
>>> + [curses_found=yes &&
>>> + AC_DEFINE([HAVE_LIBCURSES], [1],
>>> + [Define to 1 if curses is enabled.])
>>> + ])
>>
>> I don't think the `&&` is needed, you can just put each action on its
>> own line. It becomes regular shell script in the end. I tried removing
>> it on my side, it seems to work fine. If that work for you too, I can
>> push the patch with that little change.
>
> Yes, that sounds good to me. Thanks!
>
> Philippe.
Pushed, thanks!
Simon
prev parent reply other threads:[~2023-02-21 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 18:42 [PATCH] " Philippe Blain
2023-02-15 18:58 ` Simon Marchi
2023-02-15 19:54 ` Philippe Blain
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 [this message]
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=03f11e34-1a30-6712-09a2-8983e68d1a70@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=levraiphilippeblain@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).